Nokia NSS M13.5 VN Product Requirements

Data Export Date: 07 Sep 2008


1. Change History


IssueDateAuthorComments
TBD   


2. Document References


None.

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
HLR - Mapped with ACHLR.hlr_id
ACHHLRHLR.Neutral.GSM.access
HL1HLRHLR.Neutral.GSM.mobility
LAC - Mapped with VLRLAC.msc_id&"-"&lac_id
MSC - Mapped with TC.msc_id
CCMEAMSC.Neutral.GSM.call_completion
HO1MSC.Neutral.GSM.handover
NUMDMSC.Neutral.GSM.destination
SERVIMSC.Neutral.GSM.services
TCMSC.Neutral.GSM.traffic
VLR1MSCMSC.Neutral.GSM.page
Processor - Mapped with CLOM.msc_id &"-"& unit_id or CLOH.hlr_id &"-"& unit_id
CLOMProcessor.Neutral.GSM.cpu
Route_IF - Mapped with CGR.msc_id&"/"&cgr_id
CGRRoute_IF.Neutral.GSM.transmission
nc_routeRoute_IF.Neutral.GSM.transmission.forecast
nc_routeRoute_IF.Neutral.GSM.transmission
route_interface_transmission_weekRoute_IF.Neutral.GSM.transmission
systemRoute_IF.Neutral.GSM.transmission.forecast
systemRoute_IF.Neutral.GSM.transmission
Signalling_Link - Mapped with MTPMSC.msc_id &"-"& sln_id
MTPMSCSignalling_Link.Neutral.GSM.link
SLMSCSignalling_Link.Neutral.GSM.link
SLPMSCSignalling_Link.Neutral.GSM.link
Signalling_LinkSet - Mapped with AVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
AVANMSCSignalling_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
systemSignalling_LinkSet.Neutral.GSM.forecast
systemSignalling_LinkSet.Neutral.GSM.signalling_linkset
Signalling_Point - Mapped with STAMSC.msc_id&"-"&snet_id&"-"&spc_id
STAMSCSignalling_Point.Neutral.GSM.signalling_point
Signalling_RouteSet - Mapped with AVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
AVANMSCSignalling_RouteSet.Neutral.GSM.routeset
VLR - Mapped with VLR1MSC.msc_id
PLMNVVLR.Neutral.GSM.mobility
VLR1MSCVLR.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.

HLR

The Home Location Register is the main network database (may be distributed). The HLR records permanent subscriber information, and keeps track of each subscriber's status and location in the network.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR.YACHLR.hlr_id
Relationship Attributes
RegionRegion associated with the HLR.Yregion_id
NetworkNetwork associated with the HLR.Ynetwork_id
Configuration Attributes
NameA user friendly name preferably unique for the HLR. ACHLR.hlr_id
VendorManufacturer of the HLR. "Nokia"
HLR_VersionHardware/Software version of the HLR. "M13.5"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


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.YVLRLAC.msc_id&"-"&lac_id
Relationship Attributes
MSCThe MSC which controls this Location Area Code.YVLRLAC.msc_id
RegionRegion associated with the LAC.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
NetworkNetwork associated with the LAC.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the LAC. VLRLAC.msc_id&"-"&lac_id
VendorManufacturer of the LAC. "Nokia"


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.YTC.msc_id
Relationship Attributes
RegionRegion associated with the MSC.YTC.region_id
NetworkNetwork associated with the MSC.YTC.network_id
Configuration Attributes
NameA user friendly name preferably unique for the MSC. TC.msc_id
VendorManufacturer of the MSC. "Nokia"
MSC_VersionHardware/Software version of the MSC. "M13.5"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
MSC_TypeType of MSC. "Populated by customer"


Network

Network information.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Network.YTC.network_id
Configuration Attributes
NameA user friendly name preferably unique for the Network. TC.network_id
Network_TypeType of Network (e.g. GSM-900, GSM-1800 or GSM-1900). "MSC"
Default_Link_SpeedThe default speed of SS7 Signalling Links in this network. "Populated by the customer"


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.YCLOM.msc_id &"-"& unit_id or CLOH.hlr_id &"-"& unit_id
Relationship Attributes
RegionRegion associated with the Processor.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id or hlr_id)
NetworkNetwork associated with the Processor.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id or hlr_id)
Configuration Attributes
NameA user friendly name preferably unique for the Processor. CLOM.msc_id &"-"& unit_id or CLOH.hlr_id &"-"& unit_id
Processor_TypeType of Processor. CLOM or CLOH."computer_unit"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). CLOM or CLOH."GSM"
Node_IdThis is the identifier for the network element containing the Processor. CLOM.msc_id or CLOH.hlr_id
Node_NameA user friendly name preferably unique for the Node. CLOM.msc_id or CLOH.hlr_id
Node_TypeThe type of the network element containing the Processor. CLOM."MSC" OR CLOH."HLR"
Processor_VersionHardware/Software version of the Processor. "M13.5"
VendorManufacturer of the Processor. "Nokia"


Region

A user defined grouping of network elements.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDRegion associated with the network object.YTC.region_id
Relationship Attributes
NetworkNetwork associated with the Region.YTC.network_id
Configuration Attributes
NameA user friendly name preferably unique for the Region. TC.region_id


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.YCGR.msc_id&"/"&cgr_id
Relationship Attributes
RegionRegion associated with the Route IF.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
NetworkNetwork associated with the Route IF.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the Route IF. CGR.msc_id&"/"&cgr_id
Source_IdA unique identifier for the Node (Switch) at this end of the connection. CGR.msc_id
Source_TypeType of Source. "MSC"
Source_NameA user friendly name preferably unique for the Source. CGR.msc_id
Target_TypeType of Target. "To be defined"
Target_NameA user friendly name preferably unique for the Target. "To be defined"
Is_POIIs it a Point of Interconnection. "TRUE"
Is_TrunkIs it a Trunk Route? "TRUE"
Route_DirectionThere are three options - Incoming, Outgoing or BothWay. if CGRDIR_ID = 2 then "Outgoing" else if CGRDIR_ID = 1 then "Incoming" else if CGRDIR_ID = 3 then "Bothway" else "Unknown"
Route_TypeThe type of route. "To be defined"
Target_IdA unique identifier for the Node at the other end of the connection. "To be defined"
Source_TechnologyTechnology of the Source (e.g. GSM, GPRS, UMTS). "GSM"
Target_TechnologyTechnology of the Target (e.g. GSM, GPRS, UMTS). "GSM"


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.YAVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
Relationship Attributes
SS7_PointThe SS7 Point to which this SS7 LinkSet is connected to (at this end).YAVANMSC.msc_id&"-"&snet_id&"-"&spc_id
NetworkNetwork associated with the SS7 LinkSet.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
RegionRegion associated with the SS7 LinkSet.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 LinkSet. AVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
Node_IdThe Node (MSC or HLR) that this SS7 LinkSet is connected to (at this end). AVANMSC.msc_id
Node_NameName of the node that this SS7 LinkSet is connected to (at this end). AVANMSC.msc_id
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). "Populated by the customer"
Designed_Link_FailuresThe number of SS7 Link failures permitted on the SS7 LinkSet while still keeping the SS7 LinkSet up to its designed capacity. "Populated by the customer"
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). "Populated by the customer"


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.YMTPMSC.msc_id &"-"& sln_id
Relationship Attributes
SS7_LinkSetThe Node (MSC or HLR) that this SS7 Link is connected to (at this end).Y MTPMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id
SS7_PointA unique identifier for the SS7 Point.YMTPMSC.msc_id &"-"& snet_id &"-"& spc_id
RegionRegion associated with the SS7 Link.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
NetworkNetwork associated with the SS7 Link.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 Link. MTPMSC.msc_id &"-"& sln_id
Node_NameThe name for the network element that the SS7 Link is connected to (at this end). MTPMSC.msc_id
Node_IdThe Node (MSC or HLR) that this SS7 Link is connected to (at this end). MTPMSC.msc_id
Data_RateThe SS7 Link speed in bits per second (bit/s). MTPMSC.M210B1C2
Node_TypeThe type of the network element that the SS7 Link is connected to at this end. MTPMSC."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).  


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.YSTAMSC.msc_id&"-"&snet_id&"-"&spc_id
Relationship Attributes
RegionRegion associated with the SS7 Point. SS7_Point - the default value is derived via the Node.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
NetworkNetwork associated with the SS7 Point.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 Point. STAMSC.msc_id&"-"&snet_id&"-"&spc_id
Node_IdA unique identifier for the Node. STAMSC.msc_id
Node_NameA user friendly name preferably unique for the Node. msc_id
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.  


Signalling_RouteSet

A Signalling Route is a path from one point to another in the signalling network. It is implemented by a number of LinkSets, but the relationship between RouteSets and LinkSets is not available in the data supplied by most vendors.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SS7 RouteSet.YAVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
Relationship Attributes
SS7_PointThe SS7 Point to which this SS7 RouteSet is connected (at this end).YAVANMSC.msc_id&"-"&snet_id&"-"&spc_id
RegionRegion associated with the SS7 RouteSet.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), msc_id)
NetworkNetwork associated with the SS7 RouteSet.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 RouteSet. AVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
Node_NameA user friendly name preferably unique for the Node. lookup("nc_msc","msc_name",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), msc_id)
Node_IdThe Node that this SS7 RouteSet is connected to (at this end). AVANMSC.msc_id
Node_TypeType of Node. "MSC"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Adjacent_Node_IdThe Adjacent node that this SS7 RouteSet is connected from (at the other end).  


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.YVLR1MSC.msc_id
Relationship Attributes
MSCThe MSC to which the VLR belongs.YVLR1MSC.msc_id
NetworkNetwork associated with the VLR.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
RegionRegion associated with the VLR.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the VLR. VLR1MSC.msc_id
VLR_VersionHardware/Software version of the VLR. "M13.5"
VendorManufacturer of the VLR. "Nokia"
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.

Completion_Code

Call completion codes for voice switches.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Completion Code.YCCMEA.cc_id
Configuration Attributes
NameA user friendly name preferably unique for the Completion Code. CCMEA.cc_id
Completion_Code_TypeType of Completion Code.  
Completion_Code_DescriptionDescription of Completion Code.  


Supplementary_Service

Supplementary Services supported by voice switches.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Supplementary Service.YSERVI.service_id
Configuration Attributes
NameA user friendly name preferably unique for the Supplementary Service. SERVI.service_id


Traffic_Type

Types of traffic carried by a voice switch.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Traffic Type.YTC.TCAT_ID
Configuration Attributes
NameA user friendly name preferably unique for the Traffic Type. TC.TCAT_ID
DirectionDirection of Traffic. No mapping
IS_SwitchedIs the traffic switched? No mapping


6. Busy Hours

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

ObjectBusy HourAcronymDefining KPI
HLRbusy_hourhbhHLR.Neutral.GSM.access.auc_la_update_attempts
MSCbusy_hourmbhMSC.Neutral.GSM.traffic.traffic
MSCtraffic_type_busy_hourmtbhMSC.Neutral.GSM.traffic.traffic
Processorbusy_hourpbhProcessor.Neutral.GSM.cpu.load_pc
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.

Constant NameDescriptionUnitsDefault Value
GTP_header_Size Byte16


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.


HLR Performance Indicators

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


HLR.Neutral.GSM.access

Statistics on authentication procedures

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_auc_failurePERCENTAGEFLOATPercentage of failed requests for authentication parameters to the Authentication Centre (HLR to AUC)percentfail({HLR.Neutral.GSM.access.auc_failures}, {HLR.Neutral.GSM.access.auc_attempts})hbh
%_auc_successPERCENTAGEFLOATFailed requests for authentication parameters to the Authentication Centre (HLR to AUC)percentok({HLR.Neutral.GSM.access.auc_successes}, {HLR.Neutral.GSM.access.auc_attempts})hbh
%_auth_failurePERCENTAGEFLOATPercentage of failed requests from a VLR for authentication parameters (VLR to HLR)percentfail({HLR.Neutral.GSM.access.auth_failures}, {HLR.Neutral.GSM.access.auth_attempts})hbh
%_auth_successPERCENTAGEFLOATPercentage of successful requests from a VLR for authentication parameters (VLR to HLR)percentok({HLR.Neutral.GSM.access.auth_successes}, {HLR.Neutral.GSM.access.auth_attempts})hbh
auc_attemptsACCUMULATIONINTEGERRequests for authentication parameters to the Authentication Centre (HLR to AUC)No mappinghbh
auc_failuresACCUMULATIONINTEGERSuccessful requests for authentication parameters to the Authentication Centre (HLR to AUC)No mappinghbh
auc_la_update_attemptsACCUMULATIONINTEGERTotal auc_attempts + la_update_attempts for HLR Busy Hour{HLR.Neutral.GSM.access.auc_attempts} + {HLR.Neutral.GSM.mobility.la_update_attempts} 
auc_successesACCUMULATIONINTEGERSuccessful requests for authentication parameters to the Authentication Centre (HLR to AUC)No mappinghbh
auth_attemptsACCUMULATIONINTEGERRequests from a VLR for authentication parameters (VLR to HLR)ACHHLR.M87B3C6hbh
auth_failuresACCUMULATIONINTEGERFailed requests from a VLR for authentication parameters (VLR to HLR)ACHHLR.M87B3C6 - M87B3C7hbh
auth_reusedACCUMULATIONINTEGERNumber of times that authentication parameters have been re-usedNo mappinghbh
auth_successesACCUMULATIONINTEGERSuccessful requests from a VLR for authentication parameters (VLR to HLR)ACHHLR.M87B3C7hbh


HLR.Neutral.GSM.mobility

Statistics on the communication between VLRs and the HLR

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_active_subscribersPERCENTAGEFLOATPercentage of subscribers known to this HLR that are registered in a VLRpercentfail({HLR.Neutral.GSM.mobility.vlr_subscribers}, {HLR.Neutral.GSM.mobility.subscribers})hbh
%_inactive_subscribersPERCENTAGEFLOATPercentage of subscribers known to this HLR that are not registered in a VLRpercentfail({HLR.Neutral.GSM.mobility.subscribers} - {HLR.Neutral.GSM.mobility.vlr_subscribers}, {HLR.Neutral.GSM.mobility.subscribers})hbh
%_la_update_failurePERCENTAGEFLOATPercentage of failed requests to update a subscriber?s Location Areapercentfail({HLR.Neutral.GSM.mobility.la_update_failures}, {HLR.Neutral.GSM.mobility.la_update_attempts})hbh
%_la_update_successPERCENTAGEFLOATPercentage of successful requests to update a subscriber?s Location Areapercentok({HLR.Neutral.GSM.mobility.la_update_successes}, {HLR.Neutral.GSM.mobility.la_update_attempts})hbh
%_msrn_failurePERCENTAGEFLOATPercentage of failed requests for MSRN by a VLRpercentfail({HLR.Neutral.GSM.mobility.msrn_failures}, {HLR.Neutral.GSM.mobility.msrn_attempts})hbh
%_msrn_successPERCENTAGEFLOATPercentage of successful requests for MSRN by a VLRpercentok({HLR.Neutral.GSM.mobility.msrn_successes}, {HLR.Neutral.GSM.mobility.msrn_attempts})hbh
%_vlr_insert_failurePERCENTAGEFLOATPercentage of failed attempts to insert subscriber data in a VLRpercentfail({HLR.Neutral.GSM.mobility.vlr_insert_failures}, {HLR.Neutral.GSM.mobility.vlr_insert_attempts})hbh
%_vlr_insert_successPERCENTAGEFLOATPercentage of successful attempts to insert subscriber data in a VLRpercentok({HLR.Neutral.GSM.mobility.vlr_insert_successes}, {HLR.Neutral.GSM.mobility.vlr_insert_attempts})hbh
la_update_attemptsACCUMULATIONINTEGERRequests received to update a subscriber?s Location AreaHL1HLR.M83B5C5 + M83B5C6hbh
la_update_failuresACCUMULATIONINTEGERFailed requests to update a subscriber?s Location AreaHL1HLR.M83B5C6hbh
la_update_successesACCUMULATIONINTEGERSuccessful requests to update a subscriber?s Location AreaHL1HLR.M83B5C5hbh
msrn_attemptsACCUMULATIONINTEGERRequests for a Mobile Subscriber Roaming Number (MSRN) by a VLRNo mappinghbh
msrn_failuresACCUMULATIONINTEGERFailed requests for MSRN by a VLRNo mappinghbh
msrn_successesACCUMULATIONINTEGERSuccessful requests for MSRN by a VLRNo mappinghbh
roamersINTENSITYINTEGERSubscribers roaming outside this HLR?s area or outside this PLMN (network)HL1HLR.M83B5C1hbh
subscribersINTENSITYINTEGERSubscribers registered in this HLRNo mappinghbh
vlr_insert_attemptsACCUMULATIONINTEGERAttempts to insert subscriber data in a VLRNo mappinghbh
vlr_insert_failuresACCUMULATIONINTEGERFailed attempts to insert subscriber data in a VLRNo mappinghbh
vlr_insert_successesACCUMULATIONINTEGERSuccessful attempts to insert subscriber data in a VLRNo mappinghbh
vlr_subscribersACCUMULATIONINTEGERSubscribers known to this HLR that are registered in a VLRHL1HLR.M84B9C4hbh


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 actionsNo mappingmbh
la_updatesACCUMULATIONINTEGERUpdates from MS?s changing to this LACNo mappingmbh
periodic_updatesACCUMULATIONINTEGERPeriodic updatesNo mappingmbh
vlr_update_attemptsACCUMULATIONINTEGERAttempts to update the VLR with location information about MS?s in this LANo mappingmbh
vlr_update_failuresACCUMULATIONINTEGERFailures to update the VLR with location information about MS?s in this LANo mappingmbh
vlr_update_successesACCUMULATIONINTEGERSuccessful attempts to update the VLR with location information about MS?s in this LANo mappingmbh


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
pagesACCUMULATIONINTEGERFirst attempts to page an MS within this Location AreaNo mappingmbh
repagesACCUMULATIONINTEGERAttempts to re-page (after the first page in this LAC received no response)No mappingmbh
responsesACCUMULATIONINTEGERResponses to pagesNo mappingmbh
total_pagesACCUMULATIONINTEGERTotal attempts to page an MS within this Location AreaNo mappingmbh
unresponsesACCUMULATIONINTEGERThe number of paging attempts that received no response the MSNo mappingmbh


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_completion

How many of the calls controlled by this MSC terminated with each of the available Completion Codes (CCs)

KPITypeData TypeDescriptionDerivationAdditional Summaries
completedACCUMULATIONINTEGERNumber of calls that completed with the Completion CodeCCMEA.M131B2C1 + M131B2C2 + M131B2C3mbh


MSC.Neutral.GSM.call_setup

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

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

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_attemptsACCUMULATIONINTEGERChannel assignment attempts for originating callsNo mappingmbh
originate_failuresACCUMULATIONINTEGERFailures to assign channels for originating callsNo mappingmbh
originate_successesACCUMULATIONINTEGERSuccessful attempts to assign channels for originating callsNo mappingmbh
terminate_attemptsACCUMULATIONINTEGERChannel assignment attempts for terminating callsNo mappingmbh
terminate_failuresACCUMULATIONINTEGERFailures to assign channels for terminating callsNo mappingmbh
terminate_successesACCUMULATIONINTEGERSuccessful attempts to assign channels for terminating callsNo mappingmbh


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_callsACCUMULATIONINTEGERNumber of calls to the destination that were answeredNUMD.M17B2C7mbh
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} * {MSC.Neutral.GSM.destination.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)No mappingmbh
mean_holding_timeACCUMULATIONFLOATMean holding time of circuits to the destination({MSC.Neutral.GSM.destination.traffic} * {MSC.Neutral.GSM.destination.measurement_seconds}) / {MSC.Neutral.GSM.destination.total_calls}mbh
total_callsACCUMULATIONINTEGERNumber of calls to the destinationNUMD.M17B2C5mbh
trafficERLANGFLOATTraffic to the destination (including calls that have not been answered)NUMD.M17B2C11mbh


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 succeededpercentok({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_attemptsACCUMULATIONINTEGERHandover attempts coming in from another MSC (i.e. inter-MSC)HO1.M81B3C15 + M81B3C16mbh
incoming_intermsc_failuresACCUMULATIONINTEGERFailed incoming inter-MSC handover attempts (i.e. inter-MSC)HO1.M81B3C16mbh
incoming_intermsc_successesACCUMULATIONINTEGERSuccessful incoming inter-MSC handover attempts (i.e. inter-MSC)HO1.M81B3C15mbh
interbsc_attemptsACCUMULATIONINTEGERAttempted inter-BSC handovers controlled by this MSC (i.e. intra-MSC)HO1.M81B3C6 + M81B3C5mbh
interbsc_failuresACCUMULATIONINTEGERFailed inter-BSC handovers controlled by this MSC (i.e. intra-MSC)HO1.M81B3C6mbh
interbsc_successesACCUMULATIONINTEGERSuccessful inter-BSC handovers controlled by this MSC (i.e. intra-MSC)HO1.M81B3C5mbh
outgoing_intermsc_attemptsACCUMULATIONINTEGERHandover attempts to another MSC (i.e. inter-MSC)HO1.M81B3C23 + M81B3C24mbh
outgoing_intermsc_failuresACCUMULATIONINTEGERFailed outgoing inter-MSC handover attempts (i.e. inter-MSC)HO1.M81B3C24mbh
outgoing_intermsc_successesACCUMULATIONINTEGERSuccessful outgoing inter-MSC handover attempts (i.e. inter-MSC)HO1.M81B3C23mbh


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_pagesACCUMULATIONINTEGERFirst Global paging messages sentVLR1MSC.M82B4C8mbh
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_pagesACCUMULATIONINTEGERFirst Local paging messages sentVLR1MSC.M82B4C7mbh
local_repagesACCUMULATIONINTEGERSubsequent (repeat) Local paging messages sentVLR1MSC.M82B4C7-M82B4C3mbh
local_responsesACCUMULATIONINTEGERResponses to Local paging messagesNo mappingmbh
local_unresponsesACCUMULATIONINTEGERLocal paging messages that received no responseNo mappingmbh
total_global_pagesACCUMULATIONINTEGERFirst and subsequent Global paging messagesNo mappingmbh
total_local_pagesACCUMULATIONINTEGERFirst and subsequent Local paging messagesVLR1MSC.M82B4C7mbh


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

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
activatesACCUMULATIONINTEGERActivations of the SSSERVI.M128B2C3mbh
deactivatesACCUMULATIONINTEGERDeactivations of the SSSERVI.M128B2C4mbh
interrogationsACCUMULATIONINTEGERNumber of times that the SS was interrogatedSERVI.M128B2C5mbh
invocationsACCUMULATIONINTEGERInvocations of the SSSERVI.M128B2C2mbh


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_callsACCUMULATIONINTEGERCalls that were answeredTC.M20B2C4mbh, mtbh
call_attemptsACCUMULATIONINTEGERCall attempts in this Traffic TypeTC.M20B2C2mbh, mtbh
call_failuresACCUMULATIONINTEGERCalls that failed (all reasons)TC.M20B2C2 - M20B2C3mbh, mtbh
call_successesACCUMULATIONINTEGERCalls that were set upTC.M20B2C4mbh, mtbh
external_failed_callsACCUMULATIONINTEGERCalls that failed due to errors beyond this entity or networkTC.M20B2C6mbh, mtbh
internal_failed_callsACCUMULATIONINTEGERCalls that failed due to errors in this entity or networkTC.M20B2C5mbh, mtbh
subscriber_error_callsACCUMULATIONINTEGERFailed calls due to subscriber errorTC.M20B2C7mbh, mtbh
trafficERLANGFLOATCircuit occupancy for this Traffic TypeTC.M20B2C12/100mbh, mtbh


Processor Performance Indicators

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


Processor.Neutral.GSM.cpu

The performance (load or utilisation) of the CPU

KPITypeData TypeDescriptionDerivationAdditional Summaries
load_pcINTENSITYFLOATPercentage load of the CPU from all non-idle activities (i.e. call processing, etc.)CLOM.M119B2C2/10 or CLOH.M119B2C2/10pbh


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(route_if_id, ml_subst(gStartdate), tp_gsm_route_bh_traffic_end_date(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 requirednc_route.tp_gsm_route_bh_extra_circuits_forecast_value(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(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(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 coefficientnc_route.tp_gsm_route_bh_traffic_forecast_growth(route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_regression_errorINTENSITYFLOATForecast linear regression errornc_route.tp_gsm_route_bh_traffic_regression_error(route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_traffic_growthERLANGFLOATForecast linear traffic growthnc_route.tp_gsm_route_bh_traffic_forecast_growth(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 trafficnc_route.tp_gsm_route_bh_required_circuits_forecast_value(route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), "ml_subst(gGOS)") 
trafficERLANGFLOATForecast traffic on the routenc_route.tp_gsm_route_bh_traffic_forecast_value(route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), NULL) 
utilisationINTENSITYFLOATForecast utilisationnc_route.tp_gsm_route_bh_utilisation_forecast_value(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 circuitsCGR.M16B2C5 + M16B2C6rbh
bidsACCUMULATIONINTEGERThe number of attempts to seize a circuit (from this end)CGR.M16B2C11 + M16B2C9rbh, robh
blocked_circuitsINTENSITYFLOATNumber of circuits that are blocked or otherwise out of serviceCGR.M16B2C23-(M16B2C5 + M16B2C6)rbh
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)(ROUND(CGR.M16B2C7/100,0))rbh
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
circuitsINTENSITYINTEGERNumber of circuits provisioned on the Route for incoming and or outgoing trafficCGR.M16B2C3rbh
extra_capacity_requiredINTENSITYINTEGERForecast extra capacity requiredDECODE("ml_subst(gUser)","true","true",(DECODE((tp_gsm_route_bh_required_circuits_end_value(route_if_id, tp_gsm_route_bh_traffic_end_date(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(route_if_id, tp_gsm_route_bh_traffic_end_date(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_callsACCUMULATIONINTEGERNumber of incoming calls that were answeredCGR.M16B2C16rbh, ribh
incoming_callsACCUMULATIONINTEGERThe number of incoming calls started (i.e. circuit seizures from the other end)CGR.M16B2C12rbh, 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 RouteCGR.M16B2C24rbh, ribh
is_exhaustedINTENSITYINTEGERForecasting flag indicating if route is exhaustedDECODE(tp_gsm_route_bh_traffic_exhaustion_date(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 samplesnc_route.tp_gsm_route_bh_traffic_num_samples(route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
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_callsACCUMULATIONINTEGERNumber of outgoing calls that were answeredCGR.M16B2C17rbh, robh
outgoing_callsACCUMULATIONINTEGERThe number of successful bids (seizures) of a circuitCGR.M16B2C13rbh, robh
outgoing_congestion_timeACCUMULATIONINTEGERThe total time during the measurement period that all circuits on the Route were busy (i.e. couldn?t accept outgoing bids)CGR.M16B2C7/100/(100 *(interval*60))rbh, robh
outgoing_congestionsACCUMULATIONINTEGERThe number of bids that find that all circuits are busy. Such bids may either fail or overflow onto another Circuit GroupCGR.M16B2C9rbh, 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 RouteCGR.M16B2C25rbh, 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 + 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.link.available_time}, ({Signalling_Link.Neutral.GSM.link.available_time} + {Signalling_Link.Neutral.GSM.link.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.link.local_inhibition_time}, ({Signalling_Link.Neutral.GSM.link.available_time} + {Signalling_Link.Neutral.GSM.link.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.link.remote_inhibition_time}, ({Signalling_Link.Neutral.GSM.link.available_time} + {Signalling_Link.Neutral.GSM.link.unavailable_time}))slrbh, sltbh
%_unavailablePERCENTAGEFLOATPercentage of time (during the measurement period) that the Link was unavailablepercentfail({Signalling_Link.Neutral.GSM.link.unavailable_time}, ({Signalling_Link.Neutral.GSM.link.available_time} + {Signalling_Link.Neutral.GSM.link.unavailable_time}))slrbh, sltbh
available_timeACCUMULATIONINTEGERAmount of time the Link was available during the measurement period(SLMSC.interval*60 - M208B2C1)slrbh, sltbh
changebacksACCUMULATIONINTEGERLocal automatic changebacksSLMSC.M209B3C4slrbh, sltbh
changeoversINTENSITYFLOATLocal automatic changeoversSLMSC.M209B3C3slrbh, sltbh
congestion_lossesACCUMULATIONINTEGERNumber of congestion events that resulted in lost MSUs(SLMSC.M210B2C12 + M210B2C13 + M210B2C14)slrbh, sltbh
congestion_timeACCUMULATIONINTEGERAmount of time during which the Link was congestedSLMSC.M210B2C15 + M210B2C16 + M210B2C17slrbh, sltbh
congestionsACCUMULATIONINTEGERNumber of Link congestion indicationsSLMSC.M210B2C6 + M210B2C7 + M210B2C8slrbh, sltbh
discarded_msusACCUMULATIONINTEGERNumber of MSUs that were discarded because of Link congestionSLMSC.M210B2C9 + M210B2C10 + M210B2C11slrbh, sltbh
failures_abrACCUMULATIONINTEGERLink failures due to receipt of an abnormal FIBR or BSNRSLMSC.M209B2C3slrbh, sltbh
failures_alignmentACCUMULATIONINTEGERLink failures due to alignment or proving failureSLMSC.M209B2C7slrbh, sltbh
failures_congestionACCUMULATIONINTEGERLink failures due to the link being congested for too longSLMSC.M209B2C6slrbh, sltbh
failures_delayACCUMULATIONINTEGERLink failures due to excessive delay on ACKSLMSC.M209B2C4slrbh, sltbh
failures_error_rateACCUMULATIONINTEGERLink failures due to an excessive error rateSLMSC.M209B2C5slrbh, sltbh
failuresACCUMULATIONINTEGERLink failures (any reason)SLMSC.M209B2C2slrbh, sltbh
in_service_timeINTENSITYFLOATThe total time the Link has been up (since last reset)SLMSC.M209B2C1slrbh, sltbh
incoming_trafficACCUMULATIONINTEGERIncoming traffic receivedM210B2C2 + (6* SLPMSC.M210B2C4)slrbh
incoming_utilisationPERCENTAGEFLOATIncoming traffic utilisation ? percentage of available incoming capacity usedpercentok((8 * {Signalling_Link.Neutral.GSM.link.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_timeACCUMULATIONINTEGERAmount of time the Link was unavailable because it had failedSLPMSC.M208B2C2slrbh, sltbh
local_busy_timeACCUMULATIONINTEGERAmount of local busy timeSLPMSC.M208B2C7slrbh, sltbh
local_inhibition_timeACCUMULATIONINTEGERAmount of time the link was inhibited due to local management actionsSLPMSC.M208B2C5slrbh, sltbh
outgoing_trafficACCUMULATIONINTEGEROutgoing traffic sent(MTPMSC.M210B2C1 + (6 * M210B2C3))sltbh
outgoing_utilisationPERCENTAGEFLOATOutgoing traffic utilisation ? percentage of available outgoing capacity usedpercentok((8 * {Signalling_Link.Neutral.GSM.link.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_msusACCUMULATIONINTEGERNumber of Message Signal Units (MSUs) receivedSLPMSC.M210B2C4slrbh
received_neg_ackACCUMULATIONINTEGERNumber of negative acknowledgements (ACK) receivedSLPMSC.M209B3C2slrbh
received_sif_siosACCUMULATIONINTEGERNumber of SIF and SIO octets receivedSLPMSC.M210B2C2slrbh
received_su_errorsACCUMULATIONINTEGERNumber of Signalling Units (Sus) received with errorsSLPMSC.M209B3C1slrbh
remote_inhibition_timeACCUMULATIONINTEGERAmount of time the link was inhibited due to remote management actionsSLPMSC.M208B2C6slrbh, sltbh
remote_outage_timeACCUMULATIONINTEGERAmount of time the Link was unavailable because of a remote Processor outageSLPMSC.M208B2C4slrbh, sltbh
remote_outagesACCUMULATIONINTEGERNumber of remote Processor outagesSLPMSC.M208B2C10slrbh, sltbh
restoresACCUMULATIONINTEGERNumber of times the link was restoredSLPMSC.M209B3C5slrbh, sltbh
retransmitted_sif_siosACCUMULATIONINTEGERNumber of SIF and SIO octets re-transmittedSLPMSC.M210B2C5sltbh
transmitted_msusACCUMULATIONINTEGERNumber of Message Signal Units (MSUs) transmittedSLPMSC.M210B2C3sltbh
transmitted_sif_siosACCUMULATIONINTEGERNumber of SIF and SIO octets transmittedSLPMSC.M210B2C1sltbh
unavailable_timeACCUMULATIONINTEGERAmount of time the Link was unavailable (for any reason)SLPMSC.M208B2C1slrbh, 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(ss7_linkset_id, ml_subst(gStartdate), tp_gsm_linkset_bh_incoming_traffic_end_date(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(ss7_linkset_id, ml_subst(gStartdate), tp_gsm_linkset_bh_incoming_traffic_end_date(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 datenc_ss7_linkset.DECODE((tp_gsm_linkset_bh_incoming_traffic_exhaustion_date(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(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 coefficientnc_ss7_linkset.tp_gsm_linkset_bh_incoming_traffic_forecast_growth(ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_regression_errorINTENSITYFLOATForecast linear regression errornc_ss7_linkset.tp_gsm_linkset_bh_incoming_traffic_regression_error(ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_traffic_growthINTENSITYFLOATFroecast linear traffic growthnc_ss7_linkset.tp_gsm_linkset_bh_incoming_traffic_forecast_growth(ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
trafficACCUMULATIONFLOATForecast traffic valuenc_ss7_linkset.tp_gsm_linkset_bh_incoming_traffic_forecast_value(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_timeACCUMULATIONINTEGERTime for which the LinkSet was available(AVANMSC.interval*60)-M212B2C3slsrbh, slstbh
capacityERLANGFLOATMaximum nominal Erlangs per linksetcriticaltraffic({Signalling_LinkSet.Neutral.GSM.signalling_linkset.links}, ml_property(system.property.dnmt))slsrbh, slstbh
failuresACCUMULATIONINTEGERNumber of LinkSet failuresAVANMSC.M212B2C1slsrbh, slstbh
in_failure_capacityERLANGFLOATCapacity for the entire linkset during design link failuresss7_linkset_week.criticaltraffic(count_links, "ml_subst(gMIT)") 
incoming_trafficACCUMULATIONINTEGERTotal Incoming traffic receivedgroup({Signalling_Link.Neutral.GSM.link.incoming_traffic})slsrbh
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 exhaustednc_ss7_linkset.DECODE(tp_gsm_linkset_bh_incoming_traffic_exhaustion_date(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 LinkSetpercentok({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 Linksetgroup({Signalling_LinkSet.Neutral.GSM.signalling_linkset.available_time})slsrbh, slstbh
mean_incoming_trafficINTENSITYFLOATAverage Incoming traffic received per link{Signalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_traffic}/count(*)slsrbh
mean_outgoing_trafficINTENSITYFLOATAverage Outgoing traffic sent per link{Signalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_traffic}/count(*)slstbh
mean_unavailable_timeINTENSITYFLOATAverage Link available time for all the Links in the Linksetgroup({Signalling_LinkSet.Neutral.GSM.signalling_linkset.unavailable_time})slsrbh, slstbh
msusACCUMULATIONINTEGERForecast number of Message Signal Units (MSUs)tp_gsm_linkset_bh_received_msus_end_value(ss7_linkset_id, tp_gsm_linkset_bh_incoming_traffic_end_date(ss7_linkset_id,ml_subst(gStartdate),ml_subst(gEnddate),ml_subst(gDataCoverage)), "ml_subst(gNMT)", ml_property(system.property.dnmt)) 
number_of_samplesINTENSITYINTEGERForecast number of samplesnc_ss7_linkset.tp_gsm_linkset_bh_incoming_traffic_num_samples(ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
outgoing_trafficACCUMULATIONINTEGERTotal Outgoing traffic sentgroup({Signalling_Link.Neutral.GSM.link.outgoing_traffic})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 LinkSetgroup({Signalling_Link.Neutral.GSM.link.failures})slsrbh, 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_timeACCUMULATIONINTEGERTime for which the LinkSet was unavailableAVANMSC.M212B2C3slsrbh, 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 network?s performance, as seen from a Signalling Point

KPITypeData TypeDescriptionDerivationAdditional Summaries
adjacent_sp_inaccessible_timeACCUMULATIONINTEGERTime for which an adjacent Signalling Point was inaccessibleSTAMSC.M211B2C2 
adjacent_sp_inaccessibleACCUMULATIONINTEGERNumber of times an adjacent Signalling Point became inaccessibleSTAMSC.M211B2C1 
discarded_msusACCUMULATIONINTEGERNumber of Message Signal Units (MSUs) discarded due to routing errorsSTAMSC.M211B2C4 
received_tfcsACCUMULATIONINTEGERNumber of Transfer-Control (TFC) signals received, indicating RouteSet congestionSTAMSC.M211B2C3 


Signalling_RouteSet Performance Indicators

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


Signalling_RouteSet.Neutral.GSM.routeset

The performance of a set of Signalling Routes

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_availablePERCENTAGEFLOATPercentage of time (during the measurement period) that the RouteSet was availablepercentok({Signalling_RouteSet.Neutral.GSM.routeset.available_time}, ({Signalling_RouteSet.Neutral.GSM.routeset.available_time} + {Signalling_RouteSet.Neutral.GSM.routeset.unavailable_time})) 
%_unavailablePERCENTAGEFLOATPercentage of time (during the measurement period) that the RouteSet was unavailablepercentfail({Signalling_RouteSet.Neutral.GSM.routeset.available_time}, ({Signalling_RouteSet.Neutral.GSM.routeset.available_time} + {Signalling_RouteSet.Neutral.GSM.routeset.unavailable_time})) 
available_timeACCUMULATIONINTEGERTime for which the RouteSet was available(interval*60)-AVANMSC.M212B2C9 
failuresACCUMULATIONINTEGERNumber of RouteSet failuresAVANMSC.M212B2C8 
unavailable_timeACCUMULATIONINTEGERTime for which the RouteSet was unavailableAVANMSC.M212B2C9 


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 successespercentok({VLR.Neutral.GSM.mobility.vlr_update_successes}, {VLR.Neutral.GSM.mobility.vlr_update_attempts})mbh, vbh
id_request_attemptsACCUMULATIONINTEGERIdentification requests to PVLRNo mappingmbh, vbh
id_request_failuresACCUMULATIONINTEGERFailed identification requests to PVLRNo mappingmbh, vbh
id_request_successesACCUMULATIONINTEGERSuccessful identification requests to PVLRNo mappingmbh, vbh
imsi_attach_attemptsACCUMULATIONINTEGERIMSI attach attemptsVLR1MSC.M82B5C101mbh, vbh
imsi_attach_failuresACCUMULATIONINTEGERFailed IMSI attach attemptsM82B5C101 - VLR1MSC.M82B5C103mbh, vbh
imsi_attach_successesACCUMULATIONINTEGERSuccessful IMSI attach attemptsVLR1MSC.M82B5C103mbh, vbh
imsi_attach_updatesACCUMULATIONINTEGERUpdates due to IMSI attachVLR1MSC.M82B5C3mbh, vbh
imsi_detachesACCUMULATIONINTEGERIMSI detach eventsVLR1MSC.M82B5C105mbh, vbh
lac_update_attemptsACCUMULATIONINTEGERLocation Area update attemptsVLR1MSC.M82B3C101+M82B3C118+M82B3C106+M82B3C110+M82B3C114+M82B3C105+M82B3C122+M82B5C101mbh, vbh
lac_update_failuresACCUMULATIONINTEGERFailed Location Area updatesM82B3C101+M82B3C118+M82B3C106+M82B3C110+M82B3C114+M82B3C105-VLR1MSC.M82B3C102+M82B3C131+M82B3C107++M82B3C111+M82B3C115+M82B3C119 +M82B3C123+M82B5C103mbh, vbh
lac_update_successesACCUMULATIONINTEGERSuccessful Location Area updatesVLR1MSC.M82B3C102+M82B3C131+M82B3C107+M82B3C111+M82B3C115+M82B3C119+M82B3C123+M82B5C103mbh, vbh
new_la_updatesACCUMULATIONINTEGERUpdates for a new Location AreaNo mappingmbh, vbh
periodic_updatesACCUMULATIONINTEGERPeriodic updatesVLR1MSC.M82B3C22mbh, vbh
vlr_subscribersACCUMULATIONINTEGERSubscribers in this VLRVLR1MSC.M80B2C5mbh, vbh
vlr_update_attemptsACCUMULATIONINTEGERIntra-VLR Location Area update attemptsVLR1MSC.M82B3C14 + M82B3C1 + M82B3C10 + M82B3C5mbh, vbh
vlr_update_failuresACCUMULATIONINTEGERIntra-VLR Location Area update failuresVLR1MSC.M82B3C14 + M82B3C1 + M82B3C10 + M82B3C5 - M82B3C15 + M82B3C11 + M82B3C2 + M82B3C31mbh, vbh
vlr_update_successesACCUMULATIONINTEGERIntra-VLR Location Area update successesVLR1MSC.M82B3C15 + M82B3C11 + M82B3C2 + M82B3C31mbh, vbh
vlr_visitorsACCUMULATIONINTEGERVisitors from other PLMNs in this VLRPLMNV.M340B2C3mbh, 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 

HLR Subscribers Graph

This graph shows the number of attached users and the % number of registered users attached.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: % Subscribers in VLRs (Line Chart)
% Subscribers in VLRsHLR.Neutral.GSM.mobility.%_active_subscribersUser-defined 
Component 2: Subscribers (Line Chart)
In HLRHLR.Neutral.GSM.mobility.subscribersUser-defined 
In all VLRsHLR.Neutral.GSM.mobility.vlr_subscribersUser-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 SelectionRegion, Signalling_LinkSet, Signalling_Point
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 SelectionRegion, Signalling_LinkSet, Signalling_Point
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 SelectionRegion, Signalling_LinkSet, Signalling_Point
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 Data Coverage Graph

This graph is a bar chart showing the percentage data coverage of a selected MSC over a selected number of days. The graph uses the MSC.Traffic table to select a single traffic type and determines the total time for which data was collected for that traffic type on the selected days. Traffic type data is reported per MSC so if data is available for one traffic type from a MSC it is available for all traffic type from 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
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Data Coverage (Bar Chart)
% Data CoverageMSC.Neutral.GSM.traffic.%_data_coverageUser-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 SelectionRegion, MSC
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 SelectionRegion, MSC
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 SelectionRegion, MSC
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 SelectionRegion, MSC
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.GSM.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 SelectionRegion, MSC, Route_IF
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 SelectionRegion, MSC, Route_IF
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 SelectionRegion, MSC, Route_IF
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 SelectionRegion, MSC, Route_IF
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 SelectionRegion, Signalling_LinkSet, Signalling_Point
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 SelectionRegion, Signalling_LinkSet, Signalling_Point
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 SelectionRegion, Signalling_LinkSet, Signalling_Point
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 Routeset Availability Graph

This graph shows the routeset availability for a selected SS7 routeset

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Routeset
Primary ObjectSignalling_RouteSet
Drill-down Behaviour 

Report Parameters

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

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: % Routeset Availability (Line Chart)
% AvailabilitySignalling_RouteSet.Neutral.GSM.routeset.%_availableUser-defined 
Component 2: Total Routeset Failures (Line Chart)
Total FailuresSignalling_RouteSet.Neutral.GSM.routeset.failuresUser-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 SelectionRegion, MSC, Route_IF
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
HLRHLRs ReportingHLRHLR.Neutral.GSM.access
MSCMSCs ReportingMSCMSC.Neutral.GSM.page