GSM_Nokia_NSS_M141_MPM Product Requirements

Data Export Date: 16 Mar 2009


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
ASSOIND - Mapped with M3UAMI.msc_id & "/" & assoset_id & "/" & assoind_id or M3UAHI.hlr_id & "/" & assoset_id & "/" & assoind_id or M3UASI.srr_id & "/" & assoset_id & "/" & assoind_id
M3UAMIASSOIND.Nokia.GSM.Association_Index
ASSOSET - Mapped with M3UAMS.msc_id &"-"& assoset_id or M3UAHS.hlr_id &"-"& M3UAHS.assoset_id or M3UASS.srr_id &"-"& M3UASS.assoset_id
M3UAMSASSOSET.Nokia.GSM.Association_Set
BSC - Mapped with HOBSCM.msc_id&"-"&bscm_id or CSSB.msc_id &"-"& bscm_id or HORNCM.msc_id &"-"& rncm_id
CSSBBSC.Nokia.GSM.Call_setup_service
HOBSCMBSC.Nokia.GSM.Handover
HORNCMBSC.Nokia.GSM.Handover
CAP_Error_Code - Mapped with CAPMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or CAPMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
CAPMDECCAP_Error_Code.Nokia.GSM.CAP_Operation_Error
CAP_Op_Code - Mapped with CAPMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or CAPMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
CAPMDOCCAP_Op_Code.Nokia.GSM.CAP_Operation
CDS - Mapped with IWC.cds_id or CNTLC.cds_id
CNTLCCDS.Nokia.GSM.Control_Unit
IWCCDS.Nokia.GSM.IWF
CDS_Termination_Point - Mapped with CRCDT.CDS_id & "/" & MGWMNAME_id & "/" & TERM_id
CRCDTCDS_Termination_Point.Nokia.GSM.Status
Cell - Mapped with CELLCI.msc_id&"-"&lac_id&"-"&ci_id or HO2CI.msc_id&"-"&lac_id&"-"&ci_id or HO2LAC.msc_id&"-"&lac_id&"-"&ci_id
CELLCICell.Nokia.GSM.MSC_Cell
HO2CICell.Nokia.GSM.MSC_Handover_Cell
HO2LACCell.Nokia.GSM.MSC_Cell_Handovers_NBSC
Computer_Unit - Mapped with SIPPUNIT.MSC_id & "/" & Unit_id or MLANHUTI.MSC_id & "/" & Unit_id or CLANHUTI.CDS_id & "/" & Unit_id or HLANHUTI.HLR_id & "/" & Unit_id or SIPPMETH.MSC_id & "/" & Unit_id
SIPPUNITComputer_Unit.Nokia.GSM.SIP_Protocol
SIPPUNITComputer_Unit.Nokia.GSM.TCP_Connection
D_Link - Mapped with LAPDM.msc_id & "-" & dch_id or LAPEM.msc_id & "-" & dch_id or LAPUM.msc_id & "-" & dch_id
LAPDMD_Link.Nokia.GSM.Traffic
LAPEMD_Link.Nokia.GSM.Error
LAPUMD_Link.Nokia.GSM.Utilisation
EIR_IMEI - Mapped with EIRI.hlr_id &"/"&eirlist_id&"/"&imei_id
EIRIEIR_IMEI.Nokia.GSM.EIR
Exchange_Terminal - Mapped with ETH.hlr_id&"-"&UNIT_ID&"-"&UNITTYPE_ID or ETM.msc_id&"-"&UNIT_ID&"-"&UNITTYPE_ID or ETS.srr_id&"-"&UNIT_ID&"-"&UNITTYPE_ID
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_AIS_Received
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_CRC
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_Degrade_Service
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_Disturbance
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_Frame_Alignment
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_Signal_Missing
ETHExchange_Terminal.Nokia.GSM.HLR_PCM_Statistics
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_AIS_Received
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_CRC
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_Degrade_Service
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_DTB_Disturbance
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_Frame_Alignment
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_Signal_Missing
ETMExchange_Terminal.Nokia.GSM.MSC_PCM_Statistics
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_AIS_Received
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_CRC
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_Degrade_Service
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_Disturbance
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_Frame_Alignment
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_Signal_Missing
ETSExchange_Terminal.Nokia.GSM.SRR_PCM_Statistics
FQDN - Mapped with FQDNCC.msc_id&"-"&protocol_id&"-"&fqdn_id
FQDNCCFQDN.Nokia.GSM.FQDN_Clearcodes
HLR - Mapped with ACHHLR.hlr_id or ACHDEST.hlr_id
ACHDESTHLR.Nokia.GSM.Authentication_Count
ACHHLRHLR.Nokia.GSM.Authentication_nknss
EIRHHLR.Nokia.GSM.EIR
H1BSHLR.Nokia.GSM.Mobility_Basic_Services
HL1HLRHLR.Nokia.GSM.Mobility
HLRSSHLR.Nokia.GSM.HLRU_Data
HLRVLRHLR.Nokia.GSM.VLR
LOCHLRHLR.Nokia.GSM.SCCP_Subsystem_Local_Availability
LSECHLR.Nokia.GSM.Security_Report
obsoleteHLR.Nokia.GSM.EIR
obsoleteHLR.Nokia.GSM.SPC_Authentication_Count
REJHLRHLR.Nokia.GSM.Rejected_Calls
SGSNHHLR.Nokia.GSM.SGSN_Registered_Subscribers
SINHLRHLR.Nokia.GSM.SCCP_Single_Meter
SSERVHLR.Nokia.GSM.Supplementary_Services
SUBHLRHLR.Nokia.GSM.SCCP_Subsystem
TCAPHLRHLR.Nokia.GSM.TCAP_Messages
TCAPHLRHLR.Nokia.GSM.TCAP_Performance
TCAPHLRHLR.Nokia.GSM.TCAP_Protocol_Error_In_Completion_Portion
TCAPHLRHLR.Nokia.GSM.TCAP_Protocol_Error_In_Transaction_Portion
TCAPHLRHLR.Nokia.GSM.TCAP_User_Generated_Problems
TTRAHLRHLR.Nokia.GSM.TCAP_Transaction
UTRAHLRHLR.Nokia.GSM.HLR_Signalling_Point_Traffic_User
VLRMEHLR.Nokia.GSM.Subscribers_in_VLR
VLRMSHLR.Nokia.GSM.GPRS_Subscribers
HLR_Destination - Mapped with "GT:" & IDPHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACIHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACOHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC1HDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2HDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2HDRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOHDRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & SSAPHSRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & SSAPHSUB.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1HSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2HSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOHSRC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2HSRC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IACOHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
IACIHDESHLR_Destination.Nokia.GSM.Incoming_INAP_Application_Context
IACOHDESHLR_Destination.Nokia.GSM.Outgoing_INAP_Application_Context
IDPHDESHLR_Destination.Nokia.GSM.INAP_Invocation
IOC1HDESHLR_Destination.Nokia.GSM.Incoming_INAP_Operation_Part1
IOC2HDESHLR_Destination.Nokia.GSM.Incoming_INAP_Operation_Part2
IOC2HDRCHLR_Destination.Nokia.GSM.INAP_Reject
IOCOHDESHLR_Destination.Nokia.GSM.Outgoing_INAP_Operation
IOCOHDRCHLR_Destination.Nokia.GSM.INAP_Reject
SSAPHSRCHLR_Destination.Nokia.GSM.SSAP_Reject
SSAPHSUBHLR_Destination.Nokia.GSM.SSAP_Dialogue
SSAPHSUBHLR_Destination.Nokia.GSM.SSAP_Operation_Code
HLR_INAP_Application_Context - Mapped with IACIHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACIHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or IACOHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACOHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
IACIHDACHLR_INAP_Application_Context.Nokia.GSM.Incoming_Session
IACOHDACHLR_INAP_Application_Context.Nokia.GSM.Outgoing_Session
HLR_INAP_Detection_Point - Mapped with IDPHD.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id or IDPHS.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id
IDPHDHLR_INAP_Detection_Point.Nokia.GSM.INAP_Service_Invocation
HLR_INAP_Error_Code - Mapped with IOC1HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC1HSEC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOHDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
IOC1HDECHLR_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part1
IOC2HSECHLR_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part2
IOCOHDECHLR_INAP_Error_Code.Nokia.GSM.Outgoing_Termination
HLR_INAP_Op_Code - Mapped with IOC1HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOC2HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOCOHSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOCOHDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id
IOC1HDOCHLR_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part1
IOC2HDOCHLR_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part2
IOCOHDOCHLR_INAP_Op_Code.Nokia.GSM.Outgoing_Session
HLR_SSAP_Dialogue - Mapped with SSAPHSDI.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DI_Id
SSAPHSDIHLR_SSAP_Dialogue.Nokia.GSM.Session
HLR_SSAP_Operation - Mapped with SSAPHSOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_Id
SSAPHSOCHLR_SSAP_Operation.Nokia.GSM.Session
HLR_SSAP_Provider_Abort - Mapped with SSAPHSPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
SSAPHSPAHLR_SSAP_Provider_Abort.Nokia.GSM.Session
HLR_TCAP_Provider_Abort - Mapped with IACOHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IACIHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACIHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IACOHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
IACIHDPAHLR_TCAP_Provider_Abort.Nokia.GSM.Session
IACOHDPAHLR_TCAP_Provider_Abort.Nokia.GSM.Session
Interface_LAN - Mapped with MLANHUTI.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANHUTI.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANHUTI.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANSTIF.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANSTIF.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANSTIF.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANHUEI.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANSEIF.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANHUEI.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANSEIF.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANHUEI.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANSEIF.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id
CLANHUEIInterface_LAN.Nokia.GSM.LAN_Unit_Error
CLANHUTIInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic
CLANHUTIInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic
CLANHUTIInterface_LAN.Nokia.GSM.LAN_Unit_Utilisation
CLANSEIFInterface_LAN.Nokia.GSM.LAN_Switch_Error
CLANSTIFInterface_LAN.Nokia.GSM.LAN_Switch_Received_Traffic
CLANSTIFInterface_LAN.Nokia.GSM.LAN_Switch_Transmit_Traffic
CLANSTIFInterface_LAN.Nokia.GSM.LAN_Switch_Util
MLANEMBTInterface_LAN.Nokia.GSM.LAN_EMB
Interface_MAP - Mapped with MAPMDEST.MSC_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHSN.HLR_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHNETI.HLR_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id or MAPMNETI.MSC_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id or MAPMSN.MSC_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHDTRC.HLR_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHSNRC.HLR_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTRC.MSC_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMSNRC.MSC_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHDEST.HLR_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIRC.HLR_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id
MAPHDESTInterface_MAP.Nokia.GSM.Data_Reliability
MAPHDESTInterface_MAP.Nokia.GSM.Incoming_App_Context_Part1
MAPHDESTInterface_MAP.Nokia.GSM.Incoming_App_Context_Part2
MAPHDESTInterface_MAP.Nokia.GSM.Incoming_App_Context_Part3
MAPHDESTInterface_MAP.Nokia.GSM.Incoming_Operation_Part1
MAPHDESTInterface_MAP.Nokia.GSM.Incoming_Operation_Part2
MAPHDESTInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part1
MAPHDESTInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part2
MAPHDESTInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part3
MAPHDESTInterface_MAP.Nokia.GSM.Outgoing_Operation_Part1
MAPHDESTInterface_MAP.Nokia.GSM.Outgoing_Operation_Part2
MAPHDTRCInterface_MAP.Nokia.GSM.MAP_Reject
LAC - Mapped with VLRLAC.msc_id&"-"&lac_id or PPLAC.msc_id&"-"&lac_id or VLRNLAC.msc_id&"-"&lac_id
PPLACLAC.Nokia.GSM.Paging
VLRLACLAC.Nokia.GSM.Telemetrica_Subscribers
VLRNLACLAC.Nokia.GSM.VLR_LAC
LAC_Access_Type - Mapped with LULAC.MSC_id & "/" & LAC_id & "/" & ACCESS_id
LULACLAC_Access_Type.Nokia.GSM.Location_Update
MAP_Application_Context - Mapped with MAPHDTAC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or MAPHNIAC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & AC_id or MAPHSNAC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or MAPMDTAC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or MAPMNIAC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & AC_id or MAPMSNAC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
MAPHDTACMAP_Application_Context.Nokia.GSM.Session
MAP_Error_Code - Mapped with MAPHDTEC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPHNIEC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPHSNEC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMDTEC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMNIEC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMSNEC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id
MAPHDTECMAP_Error_Code.Nokia.GSM.Error
MAP_Operation_Code - Mapped with MAPHDTOC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or MAPHNIOC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & OC_id or MAPHSNOC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or MAPMDTOC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or MAPMNIOC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & OC_id or MAPMSNOC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
MAPHDTOCMAP_Operation_Code.Nokia.GSM.Operations
MAP_Provider_Abort - Mapped with MAPHDTPA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_id or MAPHNIPA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & PA_id or MAPHSNPA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_id or MAPMDTPA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_id or MAPMNIPA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & PA_id or MAPMSNPA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_id
MAPHDTPAMAP_Provider_Abort.Nokia.GSM.Application_Context_Abort
MAP_User_Abort - Mapped with MAPHDTUA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & UA_id or MAPHNIUA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & UA_id or MAPHSNUA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & UA_id or MAPMDTUA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & UA_id or MAPMNIUA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & UA_id or MAPMSNUA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & UA_id
MAPHDTUAMAP_User_Abort.Nokia.GSM.Application_Context_Abort
MGW - Mapped with MEG.mgwmname_id OR IPATM.mgwmname_id&"-"&nmgwname_id or CRCDT.mgwmname_id or MGWTCP.PMGW_ID or MGWTCV.PMGW_ID or SIMCMGW.PMGW_ID or CRTERM.mgwmname_id or EVEM.mgwmname_id or NMGW.mgwmname_id or UPD.mgwmname_id
CRTERMMGW.Nokia.GSM.MSC_circuit_seizure_supervision
EVEMMGW.Nokia.GSM.MSC_MGW_Events
IPATMMGW.Nokia.GSM.IP_ATM_traffic
MEGMGW.Nokia.GSM.Megaco
MGWTCPMGW.Nokia.GSM.Traffic
NMGWMGW.Nokia.GSM.Handover
obsoleteMGW.Nokia.GSM.Circuit_Seizure_Supervision
SIMCMGWMGW.Nokia.GSM.Simultaneous_Calls
UPDMGW.Nokia.GSM.UPD
MGW_Neighbour - Mapped with SMGW.msc_id & "-" & mgwm_id & "-" & nmgwm_id
SMGWMGW_Neighbour.Nokia.GSM.Handover
MSC - Mapped with TC.msc_id or MLANEMB.msc_id or SIMCMSC.msc_id or SIPPROT.msc_id or ANN.msc_id
ANNMSC.Nokia.GSM.Integrated_Announcement_Device
CC1MSC.Nokia.GSM.Signal_Clear_Code_Group
CC2MSC.Nokia.GSM.Signal_Clear_Code
CCDESMSC.Nokia.GSM.Clear_Code_Destination
CCMEAMSC.Nokia.GSM.Clear_Code
CELLMSCMSC.Nokia.GSM.Cell
CNTLMSC.Nokia.GSM.Control_Unit
CNTLLMMSC.Nokia.GSM.Control_Unit_Load
CSSMMSC.Nokia.GSM.CSSMT
CSTSMSC.Nokia.GSM.CSTS
CSTSUMSC.Nokia.GSM.Setups
DATAMSC.Nokia.GSM.Data_Clear_Code
DCALLMSC.Nokia.GSM.Data_Clear_Code_Destination
DESTCGMSC.Nokia.GSM.Clear_Code_Group_Destination
DSEMSC.Nokia.GSM.Data_Service
DTDMSC.Nokia.GSM.Destination_to_Destination
GBSAIURMSC.Nokia.GSM.GBS_Data_AIUR
GBSFNURMSC.Nokia.GSM.GBS_Data_FNUR
HO1MSC.Nokia.GSM.GSM_UMTS_Handovers
HO1MSC.Nokia.GSM.Handover
HO1MSC.Nokia.GSM.Intra_GSM_Handovers
HO1MSC.Nokia.GSM.Intra_UMTS_Handovers
HO1MSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN
HO1MSC.Nokia.GSM.UMA_handovers_inter_MSC
HO1MSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC
HO1MSC.Nokia.GSM.UMA_handovers_intra_MSC
HO1MSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN
HO1MSC.Nokia.GSM.UMTS_GSM_Handovers
INDMSC.Nokia.GSM.Gapped_In_Services_Destination
INGAPMSC.Nokia.GSM.Gapped_in_Services
INSMSC.Nokia.GSM.Gapped_In_Services_Service
IWFCTMSC.Nokia.GSM.IWF_Calltype
LAPDMSCRMSC.Nokia.GSM.LAPD_Traffic
LAPEMSCRMSC.Nokia.GSM.LAPD_Error
LAPUMSCRMSC.Nokia.GSM.LAPD_Utilisation
LOCMSCMSC.Nokia.GSM.SCCP_Subsystem_Local_Availability
MGWCUMSC.Nokia.GSM.Codec_usage
MLANEMBMSC.Nokia.GSM.LAN_Ethernet_Msg_Bus
MSCPPLMSC.Nokia.GSM.Paging_LAC
MSCTRAFMSC.Nokia.GSM.Trafficability
MSCVLRMSC.Nokia.GSM.Subscribers_HLR
NUMDMSC.Nokia.GSM.Number_Destination
NUPDMSC.Nokia.GSM.MSC_UPD
obsoleteMSC.Nokia.GSM.Circuit_Seizure_Supervision
obsoleteMSC.Nokia.GSM.FQDN_Clearcodes
obsoleteMSC.Nokia.GSM.Signal_Clear_Code_Circuit_Group
PRCAMSC.Nokia.GSM.Priority_calls
REJMSCMSC.Nokia.GSM.Rejected_Calls
ROUTMSCMSC.Nokia.GSM.Routing
SERVIMSC.Nokia.GSM.Subscriber_Facilities
SIMCMSCMSC.Nokia.GSM.Simultaneous_Calls
SINMSCMSC.Nokia.GSM.SCCP_Single_Meter
SIPMMSC.Nokia.GSM.SIP_registration
SIPPROTMSC.Nokia.GSM.STU_Restart
SSECMSC.Nokia.GSM.Security_Report
SUBMSCMSC.Nokia.GSM.SCCP_Subsystem
TCMSC.Nokia.GSM.Traffic_Category
TCAPMSCMSC.Nokia.GSM.TCAP_Messages
TCAPMSCMSC.Nokia.GSM.TCAP_Performance
TCAPMSCMSC.Nokia.GSM.TCAP_Protocol_Error_In_Completion_Portion
TCAPMSCMSC.Nokia.GSM.TCAP_Protocol_Error_In_Transaction_Portion
TCAPMSCMSC.Nokia.GSM.TCAP_User_Generated_Problems
TCGRPMSC.Nokia.GSM.Traffic_Category_All_Types
TRFOMSC.Nokia.GSM.TRFO
TTRAMSCMSC.Nokia.GSM.TCAP_Transaction
UMTSAIMSC.Nokia.GSM.GBS_Data_UMTS_AIUR
UMTSFNMSC.Nokia.GSM.GBS_Data_UMTS_FNUR
UTRAMSCMSC.Nokia.GSM.MSC_Signalling_Pt_Traffic_User
MSC_CAP_Application_Context - Mapped with CAPMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or CAPMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
CAPMDACMSC_CAP_Application_Context.Nokia.GSM.Session
MSC_Destination - Mapped with "GT:" & IDPMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACIMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & SSAPMSUB.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & CAPMSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IACOMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC1MSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2MSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2MSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOMSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & CAPMDEST.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC1MDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2MDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IACOMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
CAPMDESTMSC_Destination.Nokia.GSM.CAP_Invocation
CAPMDESTMSC_Destination.Nokia.GSM.Incoming_CAP_Application_Context
CAPMDESTMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1
CAPMDESTMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2
CAPMDESTMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3
CAPMDESTMSC_Destination.Nokia.GSM.Outgoing_CAP_Application_Context
CAPMDESTMSC_Destination.Nokia.GSM.Outgoing_CAP_Operation
CAPMDRCMSC_Destination.Nokia.GSM.CAP_Reject_cause
IACIMDESMSC_Destination.Nokia.GSM.INAP_Incoming_App_Context
IACOMDESMSC_Destination.Nokia.GSM.INAP_Outgoing_App_Context
IDPMDESMSC_Destination.Nokia.GSM.INAP_Invocation
IOC1MDESMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part1
IOC2MDESMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part2
IOC2MDRCMSC_Destination.Nokia.GSM.INAP_Incoming_Reject_Cause
IOCOMDESMSC_Destination.Nokia.GSM.INAP_Outgoing_Op_Code
IOCOMDRCMSC_Destination.Nokia.GSM.INAP_Outgoing_Reject_Cause
SSAPMSRCMSC_Destination.Nokia.GSM.SSAP_Reject
SSAPMSUBMSC_Destination.Nokia.GSM.SSAP_Dialogue
SSAPMSUBMSC_Destination.Nokia.GSM.SSAP_Operation_Code
MSC_Detection_Point - Mapped with IDPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id or IDPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id or CAPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id or CAPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id
CAPMDMSC_Detection_Point.Nokia.GSM.CAP_Service_Invocation
IDPMDMSC_Detection_Point.Nokia.GSM.INAP_Service_Invocation
MSC_INAP_Application_Context - Mapped with IACIMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACIMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or IACOMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACOMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
IACIMDACMSC_INAP_Application_Context.Nokia.GSM.Incoming_Session
IACOMDACMSC_INAP_Application_Context.Nokia.GSM.Outgoing_Session
MSC_INAP_Error_Code - Mapped with IOC1MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC1MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC2MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOCOMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
IOC1MDECMSC_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part1
IOC2MSECMSC_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part2
IOCOMDECMSC_INAP_Error_Code.Nokia.GSM.Outgoing_Termination
MSC_INAP_Op_Code - Mapped with IOC1MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOC2MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOCOMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC2MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOCOMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
IOC1MDOCMSC_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part1
IOC2MDOCMSC_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part2
IOCOMDOCMSC_INAP_Op_Code.Nokia.GSM.Outgoing_Session
MSC_SSAP_Dialogue - Mapped with SSAPMSDI.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DI_Id
SSAPMSDIMSC_SSAP_Dialogue.Nokia.GSM.Session
MSC_SSAP_Operation - Mapped with SSAPMSOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_Id
SSAPMSOCMSC_SSAP_Operation.Nokia.GSM.Session
MSC_SSAP_Provider_Abort - Mapped with SSAPMSPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
SSAPMSPAMSC_SSAP_Provider_Abort.Nokia.GSM.Session
MSC_TCAP_Provider_Abort - Mapped with IACIMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACIMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id or CAPMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or CAPMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id or IACOMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACOMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id
CAPMDPAMSC_TCAP_Provider_Abort.Nokia.GSM.CAP_Provider_Abort
IACIMDPAMSC_TCAP_Provider_Abort.Nokia.GSM.INAP_Incoming_Provider_Abort
IACOMDPAMSC_TCAP_Provider_Abort.Nokia.GSM.INAP_Outgoing_Provider_Abort
Neighbour - Mapped with HO2NCI.msc_id &"-"& lac_id &"-"& ci_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id or HO2NCM.msc_id &"-"& mccm_id &"-"& mncm_id &"-"& lac_id &"-"& ci_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id
HO2NCINeighbour.Nokia.GSM.MSC_Handover_Neighbour_Cell
HO2NCMNeighbour.Nokia.GSM.msc_cell_cell_handovers
Neighbour_BSC - Mapped with BRC.msc_id &"-"& bscm_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nrncm_id or BS.msc_id &"-"& bscm_id &"-"& nbscm_id or HMRBC1.msc_id &"-"& mccm_id &"-"& mncm_id&"-"& rncm_id&"-"& nbscm_id or HMRRC.msc_id &"-"& rncm_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nrncm_id
BRCNeighbour_BSC.Nokia.GSM.Handover_RNC
BSNeighbour_BSC.Nokia.GSM.Handover_BSC
HMRBC1Neighbour_BSC.Nokia.GSM.Handover_Neighbour_BSC
HMRRCNeighbour_BSC.Nokia.GSM.Handover_Neighbour_RNC
PIU - Mapped with MLANSAPI.MSC_id & "/" & Unit_id & "/" & PIU_id or CLANSAPI.CDS_id & "/" & Unit_id & "/" & PIU_id or HLANSAPI.HLR_id & "/" & Unit_id & "/" & PIU_id
CLANSAPIPIU.Nokia.GSM.LAN_Switch_Availability
Processor - Mapped with RESMSC.msc_id&"-"&unit_id OR MBSRR.srr_id&"-"&unit_id OR MBMSC.msc_id&"-"&unit_id OR MBHLR.hlr_id&"-"&unit_id OR UMBMC.cds_id&"-"&unit_id OR ULOAD.cds_id&"-"&unit_id OR CLOM.msc_id&"-"&unit_id OR CLOH.hlr_id&"-"&unit_id OR CLOS.srr_id&"-"&unit_id OR REM.msc_id&"-"&unit_id OR REH.hlr_id&"-"&unit_id OR RES.srr_id&"-"&unit_id OR RESTC.cds_id&"-"&unit_id OR RESHLR.hlr_id&"-"&unit_id OR RESSRR.srr_id&"-"&unit_id OR CDRT.msc_id&"-"&unit_id OR CDR.msc_id&"-"&unit_id OR TCPIP.msc_id&"-"&unit_id OR SIP.msc_id&"-"&unit_id
CDRProcessor.Nokia.GSM.CDRs
CDRTProcessor.Nokia.GSM.CDR_Generation
CLOHProcessor.Nokia.GSM.HLR_CPU_Load
CLOMProcessor.Nokia.GSM.MSC_CPU_Load
CLOSProcessor.Nokia.GSM.SRR_CPU_Load
MBHLRProcessor.Nokia.GSM.HLR_Message_Bus_Load
MBMSCProcessor.Nokia.GSM.MSC_Message_Bus_Load
MBSRRProcessor.Nokia.GSM.SRR_Message_Bus_Load
REHProcessor.Nokia.GSM.HLR_Rejected_Calls
REMProcessor.Nokia.GSM.MSC_Rejected_Calls
RESProcessor.Nokia.GSM.SRR_Rejected_Calls
RESHLRProcessor.Nokia.GSM.HLR_Availability
RESMSCProcessor.Nokia.GSM.MSC_Availability
RESSRRProcessor.Nokia.GSM.SRR_Availability
RESTCProcessor.Nokia.GSM.CDS_Availability
SIPProcessor.Nokia.GSM.SIP_registration
TCPIPProcessor.Nokia.GSM.TCPIP_ICP6S_ICMP_messages_received
TCPIPProcessor.Nokia.GSM.TCPIP_ICP6S_ICMP_messages_sent
TCPIPProcessor.Nokia.GSM.TCPIP_ICP6S_ICMP
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S_depreciate_address_chosen
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S_other_IF
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S_other_scope
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S_same_IF
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S_same_scope
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S_sources_rule
TCPIPProcessor.Nokia.GSM.TCPIP_IP6S
TCPIPProcessor.Nokia.GSM.TCPIP_IPS
TCPIPProcessor.Nokia.GSM.TCPIP_TCPS_congestion_windows
TCPIPProcessor.Nokia.GSM.TCPIP_TCPS_ECN
TCPIPProcessor.Nokia.GSM.TCPIP_TCPS_SYN_cache
TCPIPProcessor.Nokia.GSM.TCPIP_TCPS
TCPIPProcessor.Nokia.GSM.TCPIP_UDP6S
TCPIPProcessor.Nokia.GSM.TCPIP_UDPS
ULOADProcessor.Nokia.GSM.CDS_CPU_Load
UMBMCProcessor.Nokia.GSM.CDS_Message_Bus_Load
RNC - Mapped with CSSR.msc_id&"-"&rncm_id or RNCMCC.msc_id&"-"&rncm_id
CSSRRNC.Nokia.GSM.Call_setup_service
RNCMCCRNC.Nokia.GSM.Signalling_clear_code
Route_IF - Mapped with CGR.msc_id&"/"&cgr_id or CGRCC.msc_id&"/"&cgr_id or CGRC.cds_id&"/"&cgr_id or CSTSC.msc_id&"/"&cgr_id or CTD.msc_id&"/"&cgr_id or LOADM.msc_id&"/"&cgr_id or PRCAR.msc_id&"/"&route_id or ROU.msc_id&"/"&dest_id&"/"&subdest_id&"/"&route_id or ROUTDM.msc_id&"/"&dest_id&"/"&alt_id&"/"&dtype_id&"/"&did_id&"/"&dmode_id
CGRRoute_IF.Nokia.GSM.MSC_Circuit_Group
CGRCRoute_IF.Nokia.GSM.CDS_Circuit_Group
CGRCCRoute_IF.Nokia.GSM.Signal_Clear_Code_Ckt_Group
CSTSCRoute_IF.Nokia.GSM.Setups
CTDRoute_IF.Nokia.GSM.Circuit_Group_to_Destination
LOADMRoute_IF.Nokia.GSM.Circuit_Load
PRCARRoute_IF.Nokia.GSM.Priority_calls
ROURoute_IF.Nokia.GSM.Traffic
ROUTDMRoute_IF.Nokia.GSM.Routing_Component
Signalling_Link - Mapped with MTPHLR.hlr_id &"-"& sln_id or MTPMSC.msc_id &"-"& sln_id or MTPSRR.srr_id &"-"& sln_id or SLHLR.hlr_id &"-"& sln_id or SLMSC.msc_id &"-"& sln_id or SLPHLR.hlr_id &"-"& sln_id or SLPMSC.msc_id &"-"& sln_id or SLPSRR.srr_id &"-"& sln_id or SLSRR.srr_id &"-"& sln_id or SLAHLR.hlr_id &"-"& sln_id or SLAMSC.msc_id &"-"& sln_id or SLASRR.srr_id &"-"& sln_id or MTPNHLR.hlr_id &"-"& sln_id or MTPNMSC.msc_id &"-"& sln_id or SLPNHLR.hlr_id &"-"& sln_id or SLPNMSC.msc_id &"-"& sln_id or SLPNSRR.srr_id &"-"& sln_id or MTPNSRR.srr_id &"-"& sln_id
MTPHLRSignalling_Link.Nokia.GSM.HLR_Signalling_Link_Utilisation
MTPMSCSignalling_Link.Nokia.GSM.MSC_Signalling_Link_Utilisation
MTPNHLRSignalling_Link.Nokia.GSM.HLR_Signalling_Point_Util_2
MTPNMSCSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2
MTPNSRRSignalling_Link.Nokia.GSM.SRR_Signalling_Point_Util_2
MTPSRRSignalling_Link.Nokia.GSM.SRR_Signalling_Link_Utilisation
SLAHLRSignalling_Link.Nokia.GSM.HLR_Signalling_Link_Avail_2
SLAMSCSignalling_Link.Nokia.GSM.MSC_Signalling_Link_Avail_2
SLASRRSignalling_Link.Nokia.GSM.SRR_Signalling_Link_Avail_2
SLHLRSignalling_Link.Nokia.GSM.HLR_Signalling_Link_Availability
SLMSCSignalling_Link.Nokia.GSM.MSC_Signalling_Link_Availability
SLPHLRSignalling_Link.Nokia.GSM.HLR_Signalling_Link_Performance
SLPMSCSignalling_Link.Nokia.GSM.MSC_Signalling_Link_Performance
SLPNHLRSignalling_Link.Nokia.GSM.HLR_Signalling_point_perform_2
SLPNMSCSignalling_Link.Nokia.GSM.MSC_Signalling_point_perform_2
SLPNSRRSignalling_Link.Nokia.GSM.SRR_Signalling_point_perform_2
SLPSRRSignalling_Link.Nokia.GSM.SRR_Signalling_Link_Performance
SLSRRSignalling_Link.Nokia.GSM.SRR_Signalling_Link_Availability
Signalling_LinkSet - Mapped with AVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id or AVANHLR.hlr_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id or AVANSRR.srr_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id
AVANHLRSignalling_LinkSet.Nokia.GSM.HLR_Linkset_and_Routeset_Availability
AVANMSCSignalling_LinkSet.Nokia.GSM.MSC_Linkset_and_Routeset_Availability
AVANSRRSignalling_LinkSet.Nokia.GSM.SRR_Linkset_and_Routeset_Availability
obsoleteSignalling_LinkSet.Nokia.GSM.HLR_Signalling_LinkSet_Availability
obsoleteSignalling_LinkSet.Nokia.GSM.MSC_Signalling_LinkSet_Availability
obsoleteSignalling_LinkSet.Nokia.GSM.SRR_Signalling_LinkSet_Availability
Signalling_Point - Mapped with AVAMSC.msc_id&"-"&snet_id&"-"&spc_id or SCCPMSC.msc_id&"-"&snet_id&"-"&spc_id or AVAHLR.hlr_id&"-"&snet_id&"-"&spc_id or SCCPHLR.hlr_id&"-"&snet_id&"-"&spc_id or AVASRR.srr_id&"-"&snet_id&"-"&spc_id or SCCPSRR.srr_id&"-"&snet_id&"-"&spc_id or UTRAHLR.hlr_id &"-"& snet_id &"-"& sio_id or UTRAMSC.msc_id &"-"& snet_id &"-"& sio_id or UTRASRR.srr_id &"-"& snet_id &"-"& sio_id or ACHSPC.hlr_id&"-"&snet_id&"-"&spc_id or ACVSPC.msc_id&"-"&snet_id&"-"&spc_id or MTXMSC.msc_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXHLR.hlr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXSRR.srr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id
ACHSPCSignalling_Point.Nokia.GSM.HLR_Authentication_Count
ACVSPCSignalling_Point.Nokia.GSM.MSC_Authentication_Count
AVAHLRSignalling_Point.Nokia.GSM.HLR_Linkset_and_Routeset_Availability
AVAMSCSignalling_Point.Nokia.GSM.MSC_Linkset_and_Routeset_Availability
AVASRRSignalling_Point.Nokia.GSM.SRR_Linkset_and_Routeset_Availability
MTXHLRSignalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic_Matrix
MTXMSCSignalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic_Matrix
MTXSRRSignalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic_Matrix
obsoleteSignalling_Point.Nokia.GSM.HLR_Signalling_point_performance
obsoleteSignalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic_User
obsoleteSignalling_Point.Nokia.GSM.HLR_Signalling_Point_Utilisation
obsoleteSignalling_Point.Nokia.GSM.MSC_Signalling_point_performance
obsoleteSignalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic_User
obsoleteSignalling_Point.Nokia.GSM.MSC_Signalling_Point_Utilisation
obsoleteSignalling_Point.Nokia.GSM.SRR_Signalling_point_performance
obsoleteSignalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic_User
obsoleteSignalling_Point.Nokia.GSM.SRR_Signalling_Point_Utilisation
SCCHLRSignalling_Point.Nokia.GSM.HLR_SCCP_Signalling_Point_Subsystem
SCCMSCSignalling_Point.Nokia.GSM.MSC_SCCP_Signalling_Point_Subsystem
SCCPHLRSignalling_Point.Nokia.GSM.HLR_SCCP_Signalling_Point_Errors
SCCPHLRSignalling_Point.Nokia.GSM.HLR_SCCP_Signalling_Point_Messages
SCCPMSCSignalling_Point.Nokia.GSM.MSC_SCCP_Signalling_Point_Errors
SCCPMSCSignalling_Point.Nokia.GSM.MSC_SCCP_Signalling_Point_Messages
SCCPSRRSignalling_Point.Nokia.GSM.SRR_SCCP_Signalling_Point_Errors
SCCPSRRSignalling_Point.Nokia.GSM.SRR_SCCP_Signalling_Point_Messages
SCCSRRSignalling_Point.Nokia.GSM.SRR_SCCP_Signalling_Point_Subsystem
SIGHLRSignalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic
SIGMSCSignalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic
SIGSHLRSignalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic_STP
SIGSMSCSignalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic_STP
SIGSRRSignalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic
SIGSSRRSignalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic_STP
SPCCCSignalling_Point.Nokia.GSM.Signalling_clear_code
STAHLRSignalling_Point.Nokia.GSM.HLR_Signalling_Point_Status
STAMSCSignalling_Point.Nokia.GSM.MSC_Signalling_Point_Status
STASRRSignalling_Point.Nokia.GSM.SRR_Signalling_Point_Status
SIP_Interface - Mapped with SIPPMETH.MSC_id & "/" & Unit_id & "/" & LIF_id & "/" & ATYPE_id & "/" & CTYPE_id or SIPPRESP.MSC_id & "/" & Unit_id & "/" & LIF_id & "/" & ATYPE_id & "/" & CTYPE_id
SIPPMETHSIP_Interface.Nokia.GSM.SIP_Requests
SIPPRESPSIP_Interface.Nokia.GSM.SIP_Responses
SMSC - Mapped with SMSTY.MSC_ID&"-"&SMSCM_ID&"-"&TYPE_ID or SMS.MSC_ID&"-"&SMS.SMSCM_ID&"-ALL_TYPES" or SMSTY_AGGR.MSC_ID&"-"&SMSCM_ID&"-ALL_TYPES"
SMSSMSC.Nokia.GSM.SMS_Measurements_All_MSC_Types
SMSTYSMSC.Nokia.GSM.SMS_Measurements
SONET_SDH_Protection_Group - Mapped with SONSDH.MSC_id & "/" & PGI_id
SONSDHSONET_SDH_Protection_Group.Nokia.GSM.Protection
SRR - Mapped with REJSRR.srr_id or SRRM.srr_id or LOCSRR.srr_id or SCCPSRR.srr_id or AVASRR.srr_id or SCCSRR.srr_id or STASRR.srr_id or SIGSSRR.srr_id or SIGSRR.srr_id or MTXSRR.srr_id
LOCSRRSRR.Nokia.GSM.SCCP_Subsystem_Local_Availability
REJSRRSRR.Nokia.GSM.Rejected_Calls
RSECSRR.Nokia.GSM.Security_Report
SINSRRSRR.Nokia.GSM.SCCP_Single_Meter
SRRMSRR.Nokia.GSM.Operation_AnyTimeInterrogation
SRRMSRR.Nokia.GSM.Operation_CCBS_Request
SRRMSRR.Nokia.GSM.Operation_InitialDP_CAP
SRRMSRR.Nokia.GSM.Operation_InitialDP_INAP
SRRMSRR.Nokia.GSM.Operation_RestoreData
SRRMSRR.Nokia.GSM.Operation_SendAuthenticationInfo
SRRMSRR.Nokia.GSM.Operation_SendImsi
SRRMSRR.Nokia.GSM.Operation_SendParameters
SRRMSRR.Nokia.GSM.Operation_SendRoutingInfoForSM
SRRMSRR.Nokia.GSM.Operation_SendRoutingInformationForLCS
SRRMSRR.Nokia.GSM.Operation_SendRoutingInformation
SRRMSRR.Nokia.GSM.Operation_SendRoutingInformationWithSOR
SRRMSRR.Nokia.GSM.Operation_SMDeliveryStatus
SRRMSRR.Nokia.GSM.Operation_Unknown
SRRMSRR.Nokia.GSM.Operation_UpdateGPRSLocation
SRRMSRR.Nokia.GSM.Operation_UpdateLocation
SRRMSRR.Nokia.GSM.Operation_USSD_Notify
SRRMSRR.Nokia.GSM.Operation_USSD_Request
SRRSSPSRR.Nokia.GSM.Support_Service_Long
SRRSSPSRR.Nokia.GSM.Support_Service_Short
SUBSRRSRR.Nokia.GSM.SCCP_Subsystem
TCAPSRRSRR.Nokia.GSM.TCAP_Messages
TCAPSRRSRR.Nokia.GSM.TCAP_Performance
TCAPSRRSRR.Nokia.GSM.TCAP_Protocol_Error_In_Completion_Portion
TCAPSRRSRR.Nokia.GSM.TCAP_Protocol_Error_Transaction_Portion
TCAPSRRSRR.Nokia.GSM.TCAP_User_Generated_Problems
TTRASRRSRR.Nokia.GSM.TCAP_Transaction
UTRASRRSRR.Nokia.GSM.SRR_Signalling_Pt_Traffic_User
STM1_Set - Mapped with STM1.MSC_id & "/" & SET_id
STM1STM1_Set.Nokia.GSM.Far_End
STM1STM1_Set.Nokia.GSM.Near_End
STM1STM1_Set.Nokia.GSM.Regenerator
Timeslot - Mapped with CRCDS.cds_id& "-" &pcm_id& "-" & tsl_id or CRTSL.msc_id& "-" &pcm_id& "-" & tsl_id
CRCDSTimeslot.Nokia.GSM.Circuit_Seizure_Supervision
CRTSLTimeslot.Nokia.GSM.Circuit_Seizure_Supervision
VLR - Mapped with VLR1MSC.msc_id or ACVDEST.msc_id or ACVMSC.msc_id or DESVLR.msc_id or PLMNV.msc_id or VLRMSC.msc_id or VLRNMSC.msc_id
ACVDESTVLR.Nokia.GSM.Authentication_Count
ACVMSCVLR.Nokia.GSM.Authentication
DESVLRVLR.Nokia.GSM.HLR_Subscribers
obsoleteVLR.Nokia.GSM.SPC_Authentication_Count
PLMNVVLR.Nokia.GSM.PLMN_Subscribers
VLR1MSCVLR.Nokia.GSM.Idle_time
VLR1MSCVLR.Nokia.GSM.Inter_VLR_GSM
VLR1MSCVLR.Nokia.GSM.Inter_VLR_UMTS
VLR1MSCVLR.Nokia.GSM.Intra_VLR_GSM
VLR1MSCVLR.Nokia.GSM.Intra_VLR_UMTS
VLR1MSCVLR.Nokia.GSM.PSI_Prepaging
VLR1MSCVLR.Nokia.GSM.TMSI_allocation
VLR1MSCVLR.Nokia.GSM.ULMC
VLR1MSCVLR.Nokia.GSM.UMA_location_updates
VLR1MSCVLR.Nokia.GSM.VLR_Alternate_Paging
VLR1MSCVLR.Nokia.GSM.VLR_Departing_Subscribers
VLR1MSCVLR.Nokia.GSM.VLR_GPRS_GSM_UMTS
VLR1MSCVLR.Nokia.GSM.VLR_IMSI
VLR1MSCVLR.Nokia.GSM.VLR_Location_Updates
VLR1MSCVLR.Nokia.GSM.VLR_Paging
VLR1MSCVLR.Nokia.GSM.VLR_Resources
VLR1MSCVLR.Nokia.GSM.VLR_Search
VLR1MSCVLR.Nokia.GSM.VLR_SGSN
VLR1MSCVLR.Nokia.GSM.VLR_subscribers
VLR1MSCVLR.Nokia.GSM.VLR_TMS1
VLR1MSCVLR.Nokia.GSM.VLR_TMS2
VLR1MSCVLR.Nokia.GSM.VLR_TMS3
VLR1MSCVLR.Nokia.GSM.VLR_UMTS
VLRMSCVLR.Nokia.GSM.TM_Subscribers
VLRNMSCVLR.Nokia.GSM.Subscribers
VMGW - Mapped with MGWTCV.MSC_id & "/" & PMGW_id & "/" & VMGW_id
MGWTCVVMGW.Nokia.GSM.Traffic
VMSC - Mapped with VMSCT.msc_id & "/" & vmsc_id
VMSCTVMSC.Nokia.GSM.Call_and_Traffic


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.

ASSOIND

Association Index

In the network hierarchy, the immediate parent of the ASSOIND object is ASSOSET.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Association Index.YM3UAMI.msc_id & "/" & assoset_id & "/" & assoind_id or M3UAHI.hlr_id & "/" & assoset_id & "/" & assoind_id or M3UASI.srr_id & "/" & assoset_id & "/" & assoind_id
Relationship Attributes
ASSOSETThe ASSOSET to which the ASSOIND belongs.YM3UAMI.msc_id & "-" & assoset_id or M3UAHI.hlr_id & "-" & assoset_id or M3UASI.srr_id & "-" & assoset_id
MSCThe MSC to which the ASSOIND belongs.YM3UAMI.msc_id
RegionRegion associated with the ASSOIND.Ylookup("nc_msc","region_id",utime(M3UAMI.StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or lookup("nc_hlr","region_id",utime(M3UAHI.StartDate & " " & StartTime,"%Y-%m-%d %R"),hlr_id) or lookup("nc_srr","region_id",utime(M3UASI.StartDate & " " & StartTime,"%Y-%m-%d %R"),srr_id)
NetworkNetwork associated with the ASSOIND.Ylookup("nc_msc","network_id",utime(M3UAMI.StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or lookup("nc_hlr","network_id",utime(M3UAHI.StartDate & " " & StartTime,"%Y-%m-%d %R"),hlr_id) or lookup("nc_srr","network_id",utime(M3UASI.StartDate & " " & StartTime,"%Y-%m-%d %R"),srr_id)
Configuration Attributes
NameA user friendly name preferably unique for the ASSOIND. M3UAMI.msc_id & "-" & assoset_id & "-" & assoind_id or M3UAHI.hlr_id & "-" & assoset_id & "-" & assoind_id or M3UASI.srr_id & "-" & assoset_id & "-" & assoind_id
Node_IdNode associated with the ASSOIND M3UAMI.MSC_id or M3UAHI.HLR_id or M3UASI.SRR_id
Node_TypeNode type of the ASSOIND M3UAMI."MSC" or M3UAHI."HLR" or M3UASI."SRR"
ASSOIND_VersionHardware/Software version of the ASSOIND. "M14.1"
VendorManufacturer of the ASSOIND. "Nokia"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


ASSOSET

Association Set

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Association Set.YM3UAMS.msc_id &"-"& assoset_id or M3UAHS.hlr_id &"-"& M3UAHS.assoset_id or M3UASS.srr_id &"-"& M3UASS.assoset_id
Relationship Attributes
MSCThe MSC to which the ASSOSET belongs.YM3UAMS.msc_id
RegionRegion associated with the ASSOSET.Ylookup("nc_msc","region_id",utime(M3UAMS.StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or lookup("nc_hlr","region_id",utime(M3UAHS.StartDate & " " & StartTime,"%Y-%m-%d %R"),hlr_id) or lookup("nc_srr","region_id",utime(M3UASS.StartDate & " " & StartTime,"%Y-%m-%d %R"),srr_id)
NetworkNetwork associated with the ASSOSET.Ylookup("nc_msc","network_id",utime(M3UAMS.StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or lookup("nc_hlr","network_id",utime(M3UAHS.StartDate & " " & StartTime,"%Y-%m-%d %R"),hlr_id) or lookup("nc_srr","network_id",utime(M3UASS.StartDate & " " & StartTime,"%Y-%m-%d %R"),srr_id)
Configuration Attributes
NameA user friendly name preferably unique for the ASSOSET. M3UAMS.msc_id &"-"& assoset_id or M3UAHS.hlr_id &"-"& M3UAHS.assoset_id or M3UASS.srr_id &"-"& M3UASS.assoset_id
Node_IdIdentifier for the node of the Assoset M3UAMS.msc_id or M3UAHS.hlr_id or M3UASS.srr_id
Node_TypeNode Type for the ASSOSET. M3UAMS."MSC" or M3UAHS."HLR" or M3UASS."SRR"
ASSOSET_VersionHardware/Software version of the ASSOSET. "M14.1"
VendorManufacturer of the ASSOSET. "Nokia"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


BSC

The Base Station Controller provides all the control functions and physical links between the MSC (and/or SGSN) and Cell. It switches circuit/packet data & provides functions such as handover, cell configuration data & control of RF power levels in base transceiver stations.

In the network hierarchy, the immediate parents of the BSC object are SGSN and MSC.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the BSC.YHOBSCM.msc_id&"-"&bscm_id or CSSB.msc_id &"-"& bscm_id or HORNCM.msc_id &"-"& rncm_id
Relationship Attributes
SGSNA unique identifier for the SGSN.Y"To be defined"
MSCThe MSC to which this BSC is connected.YHOBSCM.msc_id or CSSB.msc_id or HORNCM.msc_id
RegionRegion associated with the BSC.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),HOBSCM.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CSSB.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),HORNCM.msc_id)
NetworkNetwork associated with the BSC.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),HOBSCM.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CSSB.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),HORNCM.msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the BSC. HOBSCM.msc_id&"-"&bscm_id or CSSB.msc_id &"-"& bscm_id or HORNCM.msc_id &"-"& rncm_id
VendorManufacturer of the BSC. "Nokia"
BSC_VersionHardware/Software version of the BSC. "To be defined"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


CAP_Error_Code

CAP Error Codes

In the network hierarchy, the immediate parent of the CAP_Error_Code object is CAP_Op_Code.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the CAP Error CodeYCAPMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or CAPMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
Relationship Attributes
CAP_Op_CodeOperation Code associated with the CAP_Error_CodeYCAPMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or CAPMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
MSC_DestinationThe Destination Id of the CAP_Error_CodeY"GT:" & CAPMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSCThe MSC to which the CAP_Error_Code belongs.YCAPMDEC.MSC_id or CAPMSEC.MSC_id
NetworkNetwork associated with the CAP_Error_Code.YCAPMDEC.Network_Id or CAPMSEC.Network_Id
RegionRegion associated with the CAP_Error_Code.YCAPMDEC.Region_Id or CAPMSEC.Region_Id
Configuration Attributes
NameA user friendly name for the CAP_Error_Code. CAPMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or CAPMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
Error_CodeError Code associated with the CAP_Error_Code CAPMDEC.EC_id or CAPMSEC.EC_id
MSC_Destination_TypeThe Destination Type of the CAP_Error_Code CAPMDEC."GT" or CAPMSEC."SPC"
TechnologyTechnology of the CAP_Error_Code CAPMDEC."GSM"
VendorManufacturer of the CAP_Error_Code CAPMDEC."Nokia"
VersionSoftware Version of the CAP_Error_Code "M14.1"


CAP_Op_Code

CAP Operation Codes

In the network hierarchy, the immediate parent of the CAP_Op_Code object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the CAP Op CodeYCAPMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or CAPMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
Relationship Attributes
MSC_DestinationThe Destination Id of the CAP_Op_CodeY"GT:" & CAPMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSCThe MSC to which the CAP_Op_Code belongs.YCAPMDOC.MSC_id or CAPMSOC.MSC_id
NetworkNetwork associated with the CAP_Op_Code.YCAPMDOC.Network_Id or CAPMSOC.Network_Id
RegionRegion associated with the CAP_Op_Code.YCAPMDOC.Region_Id or CAPMSOC.Region_Id
Configuration Attributes
NameA user friendly name for the CAP_Op_Code. CAPMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or CAPMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
MSC_Destination_TypeThe Destination Type of the CAP_Op_Code CAPMDOC."GT" or CAPMSOC."SPC"
OpCodeOperation Code associated with the CAP_Op_Code CAPMDOC.OC_id or CAPMSOC.OC_id
TechnologyTechnology of the CAP_Op_Code CAPMDOC."GSM"
VendorManufacturer of the CAP_Op_Code CAPMDOC."Nokia"
VersionSoftware Version of the CAP_Op_Code "M14.1"


CDS_Termination_Point

Termination Points associated with the CDS

In the network hierarchy, the immediate parent of the CDS_Termination_Point object is CDS.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the CDS_Termination_PointYCRCDT.CDS_id & "/" & MGWMNAME_id & "/" & TERM_id
Relationship Attributes
CDSThe CDS to which the CDS_Termination_Point belongs.YCRCDT.CDS_id
MGWThe MGW Id of the CDS_Termination_PointYCRCDT.CDS_id & "/" & MGWMNAME_id
NetworkNetwork associated with the CDS_Termination_Point.YCRCDT.Network_Id
RegionRegion associated with the CDS_Termination_Point.YCRCDT.Region_Id
Configuration Attributes
NameA user friendly name for the CDS_Termination_Point. CRCDT.CDS_id & "/" & MGWMNAME_id & "/" & TERM_id
TechnologyTechnology of the CDS_Termination_Point CRCDT."GSM"
VendorManufacturer of the CDS_Termination_Point CRCDT."Nokia"
VersionSoftware Version of the CDS_Termination_Point "M14.1"


CDS

The Circuit Switched Data Server provides an interworking function for terminating circuit switched data calls.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the CDSYIWC.cds_id or CNTLC.cds_id
Relationship Attributes
RegionRegion associated with the CDSYIWC.region_id or CNTLC.region_id
NetworkThe Network associated with the CDSYIWC.network_id or CNTLC.network_id
Configuration Attributes
NameA user-friendly name for the CDS IWC.cds_id or CNTLC.cds_id
TechnologyGSM, GPRS, UMTS, etc. "GSM"
CDS_TypeThe type of CDS "To be defined"
VendorManufacturer of the CDS "Nokia"
CDS_VersionHardware/Software version of the CDS "M14.1"


Cell

The Cell handles the radio interface to the mobile station. The Cell is the radio equipment (transceivers and antennas) needed to service each cell in the network. A group of Cells is controlled by a BSC.

In the network hierarchy, the immediate parents of the Cell object are PCU, Routing_Area, Registration_Area, BS and LAC.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Cell.YCELLCI.msc_id&"-"&lac_id&"-"&ci_id or HO2CI.msc_id&"-"&lac_id&"-"&ci_id or HO2LAC.msc_id&"-"&lac_id&"-"&ci_id
Relationship Attributes
PCUA unique identifier for the PCU.Y"To be defined"
NSVCA unique identifier for the NSVC.Y"To be defined"
Routing_AreaA unique identifier for the Routing_Area.Y"To be defined"
SGSNA unique identifier for the SGSN.Y"Populated by the customer"
Registration_AreaA unique identifier for the Registration_Area.Y"To be defined"
BSA unique identifier for the BS at which the Cell is located. The BS at which the cell is located.Y"To be defined"
LACThe Location Area Code encompassing the Cell.YCELLCI.msc_id&"-"&lac_id or HO2CI.msc_id&"-"&lac_id or HO2LAC.msc_id&"-"&lac_id
BSCA unique identifier for the BSC.Y"To be defined"
MSCA unique identifier for the MSC.YCELLCI.msc_id or HO2CI.msc_id or HO2LAC.msc_id
RegionRegion associated with the Cell.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), CELLCI.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), HO2CI.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), HO2LAC.msc_id)
NetworkNetwork associated with the Cell.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), CELLCI.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), HO2CI.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), HO2LAC.msc_id)
GPRS_CellA unique identifier for the Cell.Y"No mapping"
UMTS_CellA unique identifier for the Cell.Y"No mapping"
Configuration Attributes
NameA user friendly name preferably unique for the Cell. CELLCI.msc_id&"-"&lac_id&"-"&ci_id or HO2CI.msc_id&"-"&lac_id&"-"&ci_id or HO2LAC.msc_id&"-"&lac_id&"-"&ci_id
Cell_TypeIs the cell omni_directional, or a sector, or micro/pico/macro/umbrella cell, etc. "To be defined"
Defined_TRXNumber of defined TRX belonging to the cell. "To be defined"
Defined_TCHNumber of defined TCH channels of the Cell. "To be defined"
Defined_CCHNumber of defined CCH channels for the Cell. "To be defined"
Max_PowerThe bs_tx_pwr_max configuration attribute. "To be defined"
Segment_IdA unique identifier for the Segment. "To be defined"
Cell_VersionHardware/Software version of the Cell. "Populated by the customer"
VendorManufacturer of the Cell. "Nokia"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Cell_DescriptionDescription of Cell. "To be defined"
NSVC_CN_IdA unique identifier for the NSVC CN. "To be defined"
BVC_IdA unique identifier for the BVC. "To be defined"
Defined_PDCHDesignated Packet Data Channel. "To be defined"
Dedicated_PDCHDedicated Packet Data Channel. "To be defined"
UTRAN_Absolute_Radio_Freq_ULUL UTRAN absolute Radio Frequency Channel number. "To be defined"
UTRAN_Absolute_Radio_Freq_DLDL UTRAN absolute Radio Frequency Channel number. "To be defined"
Primary_Scrambling_CodePrimary DL scrambling code. "To be defined"
Primary_Common_Pilot_Ch_PowerPrimary CPICH channel power. "To be defined"
Primary_Sync_Ch_PowerPrimary synchronisation channel power, DL. "To be defined"
Secondary_Sync_Ch_PowerSecondary synchronisation channel power, DL. "Populated by the customer"
BCH_PowerBroadcast channel power. "To be defined"


Computer_Unit

A Computer Unit

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDPrimary identifier of the Computer Unit.YSIPPUNIT.MSC_id & "/" & Unit_id or MLANHUTI.MSC_id & "/" & Unit_id or CLANHUTI.CDS_id & "/" & Unit_id or HLANHUTI.HLR_id & "/" & Unit_id or SIPPMETH.MSC_id & "/" & Unit_id
Relationship Attributes
NetworkNetwork associated with the Computer unit.YSIPPUNIT.Network_Id or MLANHUTI.Network_Id or CLANHUTI.Network_Id or HLANHUTI.Network_Id or SIPPMETH.Network_Id
RegionRegion associated with the Computer unit.YSIPPUNIT.Region_Id or MLANHUTI.Region_Id or CLANHUTI.Region_Id or HLANHUTI.Region_Id or SIPPMETH.Region_Id
Configuration Attributes
NameMeaningful name of the Computer Unit. SIPPUNIT.MSC_id & "/" & Unit_id or MLANHUTI.MSC_id & "/" & Unit_id or CLANHUTI.CDS_id & "/" & Unit_id or HLANHUTI.HLR_id & "/" & Unit_id or SIPPMETH.MSC_id & "/" & Unit_id
Computer_Unit_TypeType or information about the computer unit. SIPPUNIT.Unit_id or MLANHUTI.Unit_id or CLANHUTI.Unit_id or HLANHUTI.Unit_id or SIPPMETH.Unit_id
Node_IdIdentifier of the Node SIPPUNIT.MSC_id or MLANHUTI.MSC_id or CLANHUTI.CDS_id or HLANHUTI.HLR_id or SIPPMETH.MSC_id
Node_NameMeaningful name of the Node. SIPPUNIT.MSC_id or MLANHUTI.MSC_id or CLANHUTI.CDS_id or HLANHUTI.HLR_id or SIPPMETH.MSC_id
Node_TypeType of the Node SIPPUNIT."MSC" or MLANHUTI."MSC" or CLANHUTI."CDS" or HLANHUTI."HLR" or SIPPMETH."MSC"
TechnologyTechnology of the node (e.g. UMTS, GPRS). SIPPUNIT."GSM"
VersionThe hardware/software version of this Computer Unit. "M14.1"


D_Link

A "D" (diagonal) link connects a secondary STP pair to a primary STP pair in a quad-link configuration. Secondary STPs within the same network are connected via a quad of "D" links. They are typically used to connect an MSC to an HLR.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the D Link.YLAPDM.msc_id & "-" & dch_id or LAPEM.msc_id & "-" & dch_id or LAPUM.msc_id & "-" & dch_id
Relationship Attributes
MSCA unique identifier for the MSC at MSC end of the D Link.YLAPDM.msc_id or LAPEM.msc_id or LAPUM.msc_id
HLRA unique identifier for the HLR at HLR end of the D Link.Y"To be defined"
RegionRegion associated with the D Link.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), LAPDM.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), LAPEM.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), LAPUM.msc_id)
NetworkNetwork associated with the D Link.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), LAPDM.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), LAPEM.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), LAPUM.msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the D Link. LAPDM.msc_id & "-" & dch_id or LAPEM.msc_id & "-" & dch_id or LAPUM.msc_id & "-" & dch_id
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


EIR_IMEI

Blacklisted IMEI numbers

In the network hierarchy, the immediate parent of the EIR_IMEI object is EIR_List.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDBlacklisted IMEI identifierYEIRI.hlr_id &"/"&eirlist_id&"/"&imei_id
Relationship Attributes
EIR_ListEIR list identifierYEIRI.hlr_id &"/"&eirlist_id
HLRHLR identifierYEIRI.hlr_id
RegionRegion identifierYlookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),EIRI.hlr_id)
NetworkNetwork identifierYlookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),EIRI.hlr_id)
Configuration Attributes
NameIMEI name EIRI.hlr_id &"/"&eirlist_id&"/"&imei_id
VendorVendor name "Nokia"
VersionVersion identifier "M14.1"
TechnologyTechnology name "GSM"


EIR_List

Black list of the IMEI numbers

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDEIR list identifierYEIRI.hlr_id &"/"&eirlist_id
Relationship Attributes
HLRHLR identifierYEIRI.hlr_id
RegionRegion identifierYlookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),EIRI.hlr_id)
NetworkNetwork identifierYlookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),EIRI.hlr_id)
Configuration Attributes
NameName of EIR list EIRI.hlr_id &"/"&eirlist_id
VersionVersion identifier "M14.1"
VendorVendor name "Nokia"
TechnologyTechnology name "GSM"


Exchange_Terminal

An Exchange Terminal

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the Exchange_TerminalYETH.hlr_id&"-"&UNIT_ID&"-"&UNITTYPE_ID or ETM.msc_id&"-"&UNIT_ID&"-"&UNITTYPE_ID or ETS.srr_id&"-"&UNIT_ID&"-"&UNITTYPE_ID
Relationship Attributes
RegionRegion associated with the Exchange_TerminalYlookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ETM.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ETH.hlr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ETS.srr_id)
NetworkThe Network associated with the Exchange_TerminalYlookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ETM.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ETH.hlr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ETS.srr_id)
Configuration Attributes
NameA user-friendly name for the Exchange_Terminal ETH.hlr_id&"-"&UNIT_ID&"-"&UNITTYPE_ID or ETM.msc_id&"-"&UNIT_ID&"-"&UNITTYPE_ID or ETS.srr_id&"-"&UNIT_ID&"-"&UNITTYPE_ID
ET_Unit_TypeThe exchange terminal unit type ETH.UNITTYPE_ID or ETM.UNITTYPE_ID or ETS.UNITTYPE_ID
ET_Unit_IndexThe exchange terminal unit index ETH.UNIT_ID or ETM.UNIT_ID or ETS.UNIT_ID
Node_IdThe identifier of the node associated with the object ETH.hlr_id or ETM.msc_id or ETS.srr_id
Node_NameThe name of the node associated with the object "To be defined"
Node_TypeThe type node associated with the object "To be defined"
Vendor_IdManufacturer of the Exchange_Terminal "Nokia"


FQDN

Fully Qualified Domain Name

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDFQDN identifierYFQDNCC.msc_id&"-"&protocol_id&"-"&fqdn_id
Relationship Attributes
RegionRegion identifierYlookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),FQDNCC.msc_id)
NetworkNetwork identifierYlookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),FQDNCC.msc_id)
Configuration Attributes
NameFQDN name FQDNCC.msc_id&"-"&protocol_id&"-"&fqdn_id
VersionVersion identifier "M14.1"
VendorVendor name "Nokia"
TechnologyTechnology name "GSM"


HLR_Destination

A destination associated with the HLR

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_DestinationY"GT:" & IDPHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACIHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACOHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC1HDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2HDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2HDRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOHDRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & SSAPHSRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & SSAPHSUB.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1HSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2HSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOHSRC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2HSRC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IACOHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
Relationship Attributes
HLRHLR associated with the HLR_DestinationYIDPHDES.HLR_id or IDPHSN.HLR_id or IACIHDES.HLR_id or IACIHSN.HLR_id
NetworkNetwork associated with the HLR_Destination.YIDPHDES.Network_id or IDPHSN.Network_id or IACIHDES.Network_id or IACIHSN.Network_id
RegionRegion associated with the HLR_Destination.YIDPHDES.Region_id or IDPHSN.Region_id or IACIHDES.Region_id or IACIHSN.Region_id
Configuration Attributes
NameA user friendly name for the HLR_Destination. "GT:" & IDPHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACIHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACOHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC1HDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2HDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2HDRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOHDES.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOHDRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & SSAPHSRC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & SSAPHSUB.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1HSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2HSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOHSRC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2HSRC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IACOHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOHSN.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
TechnologyTechnology of the HLR_Destination IDPHDES."GSM"
VendorManufacturer of the HLR_Destination IDPHDES."Nokia"
VersionSoftware Version of the HLR_Destination "M14.1"


HLR_INAP_Application_Context

A INAP Application Context associated with the HLR.

In the network hierarchy, the immediate parent of the HLR_INAP_Application_Context object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_INAP_Application_ContextYIACIHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACIHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or IACOHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACOHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
Relationship Attributes
HLR_DestinationThe HLR_Destination Id of the HLR_INAP_Application_ContextY"GT:" & IACIHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACOHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACOHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
HLRHLR associated with the HLR_INAP_Application_ContextYIACIHDAC.HLR_id or IACIHSAC.HLR_id or IACOHDAC.HLR_id or IACOHSAC.HLR_id
NetworkNetwork associated with the HLR_INAP_Application_Context.YIACIHDAC.Network_id or IACIHSAC.Network_id or IACOHDAC.Network_id or IACOHSAC.Network_id
RegionRegion associated with the HLR_INAP_Application_Context.YIACIHDAC.Region_id or IACIHSAC.Region_id or IACOHDAC.Region_id or IACOHSAC.Region_id
Configuration Attributes
NameA user friendly name for the HLR_INAP_Application_Context. IACIHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACIHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or IACOHDAC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACOHSAC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
TechnologyTechnology of the HLR_INAP_Application_Context IACIHDAC."GSM"
VendorManufacturer of the HLR_INAP_Application_Context IACIHDAC."Nokia"
VersionSoftware Version of the HLR_INAP_Application_Context "M14.1"


HLR_INAP_Detection_Point

INAP Detection Context associated with the HLR

In the network hierarchy, the immediate parent of the HLR_INAP_Detection_Point object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR INAP Detection PointYIDPHD.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id or IDPHS.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR INAP_Detection_PointY"GT:" & IDPHD.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPHS.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
HLRThe HLR to which the HLR INAP_Detection_Point belongs.YIDPHD.HLR_id or IDPHS.HLR_id
NetworkNetwork associated with the HLR INAP_Detection_Point.YIDPHD.Network_Id or IDPHS.Network_Id
RegionRegion associated with the HLR INAP_Detection_Point.YIDPHD.Region_Id or IDPHS.Region_Id
Configuration Attributes
NameA user friendly name for the HLR INAP_Detection_Point. IDPHD.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id or IDPHS.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id
Detection_PointDetection Point associated with the HLR INAP_Detection_Point IDPHD.DP_id or IDPHS.DP_id
HLR_Destination_TypeThe Destination Type of the HLR INAP_Detection_Point IDPHD."GT" or IDPHS."SPC"
TechnologyTechnology of the HLR INAP_Detection_Point IDPHD."GSM"
VendorManufacturer of the HLR INAP_Detection_Point IDPHD."Nokia"
VersionSoftware Version of the HLR INAP_Detection_Point "M14.1"


HLR_INAP_Error_Code

INAP Error code associated with the HLR

In the network hierarchy, the immediate parent of the HLR_INAP_Error_Code object is HLR_INAP_Op_Code.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_INAP_Error_Code.YIOC1HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC1HSEC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOHDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR_INAP_Error_CodeY"GT:" & IOC1HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1HSEC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
HLR_INAP_Op_CodeThe Operation Code Id of the HLR_INAP_Error_CodeYIOC1HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1HSEC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
HLRThe HLR to which the HLR_INAP_Error_Code belongs.YIOC1HDEC.HLR_id or IOC1HSEC.HLR_id
NetworkNetwork associated with the HLR_INAP_Error_Code.YIOC1HDEC.Network_Id or IOC1HSEC.Network_Id
RegionRegion associated with the HLR_INAP_Error_Code.YIOC1HDEC.Region_Id or IOC1HSEC.Region_Id
Configuration Attributes
NameA user friendly name for the HLR_INAP_Error_Code. IOC1HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC1HSEC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2HDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOHDEC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
ErrorCodeError Code associated with the HLR_INAP_Error_Code IOC1HDEC.EC_id or IOC1HSEC.EC_id
HLR_Destination_TypeThe Destination Type of the HLR_INAP_Error_Code IOC1HDEC."GT" or IOC1HSEC."SPC"
TechnologyTechnology of the HLR_INAP_Error_Code IOC1HDEC."GSM"
VendorManufacturer of the HLR_INAP_Error_Code IOC1HDEC."Nokia"
VersionSoftware Version of the HLR_INAP_Error_Code "M14.1"


HLR_INAP_Op_Code

INAP Operation Code associated the HLR

In the network hierarchy, the immediate parent of the HLR_INAP_Op_Code object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_INAP_Op_Code.YIOC1HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOC2HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOCOHSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOCOHDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR_INAP_Op_CodeY"GT:" & IOC1HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
HLRThe HLR to which the HLR_INAP_Op_Code belongs.YIOC1HDOC.HLR_id or IOC1HSOC.HLR_id
NetworkNetwork associated with the HLR_INAP_Op_Code.YIOC1HDOC.Network_Id or IOC1HSOC.Network_Id
RegionRegion associated with the HLR_INAP_Op_Code.YIOC1HDOC.Region_Id or IOC1HSOC.Region_Id
Configuration Attributes
NameA user friendly name for the HLR_INAP_Op_Code. IOC1HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOC2HSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOCOHSOC.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2HDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOCOHDOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id
HLR_Destination_TypeThe Destination Type of the HLR_INAP_Op_Code IOC1HDOC."GT" or IOC1HSOC."SPC"
OpCodeOperation Code associated with the HLR_INAP_Op_Code IOC1HDOC.OC_id or IOC1HSOC.OC_id
TechnologyTechnology of the HLR_INAP_Op_Code IOC1HDOC."GSM"
VendorManufacturer of the HLR_INAP_Op_Code IOC1HDOC."Nokia"
VersionSoftware Version of the HLR_INAP_Op_Code "M14.1"


HLR_SSAP_Dialogue

SSAP Dialogue associated with the HLR

In the network hierarchy, the immediate parent of the HLR_SSAP_Dialogue object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_SSAP_Dialogue.YSSAPHSDI.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DI_Id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR_SSAP_DialogueY"GT:" & SSAPHSDI.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
HLRThe HLR to which the HLR_SSAP_Dialogue belongs.YSSAPHSDI.HLR_id
NetworkNetwork associated with the HLR_SSAP_Dialogue.YSSAPHSDI.Network_Id
RegionRegion associated with the HLR_SSAP_Dialogue.YSSAPHSDI.Region_Id
Configuration Attributes
NameA user friendly name for the HLR_SSAP_Dialogue. SSAPHSDI.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DI_Id
DialogueDialogue associated with the HLR_SSAP_Dialogue SSAPHSDI.DI_Id
HLR_Destination_TypeThe Destination Type of the HLR_SSAP_Dialogue SSAPHSDI."GT"
TechnologyTechnology of the HLR_SSAP_Dialogue SSAPHSDI."GSM"
VendorManufacturer of the HLR_SSAP_Dialogue SSAPHSDI."Nokia"
VersionSoftware Version of the HLR_SSAP_Dialogue "M14.1"


HLR_SSAP_Operation

SSAP Operation code associated with the HLR

In the network hierarchy, the immediate parent of the HLR_SSAP_Operation object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_SSAP_Operation code.YSSAPHSOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_Id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR_SSAP_OperationY"GT:" & SSAPHSOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
HLRThe HLR to which the HLR_SSAP_Operation belongs.YSSAPHSOC.HLR_id
NetworkNetwork associated with the HLR_SSAP_Operation.YSSAPHSOC.Network_Id
RegionRegion associated with the HLR_SSAP_Operation.YSSAPHSOC.Region_Id
Configuration Attributes
NameA user friendly name for the HLR_SSAP_Operation code. SSAPHSOC.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_Id
HLR_Destination_TypeThe Destination Type of the HLR_SSAP_Operation SSAPHSOC."GT"
OperationOperation Code associated with the HLR_SSAP_Operation SSAPHSOC.OC_Id
TechnologyTechnology of the HLR_SSAP_Operation SSAPHSOC."GSM"
VendorManufacturer of the HLR_SSAP_Operation SSAPHSOC."Nokia"
VersionSoftware Version of the HLR_SSAP_Operation "M14.1"


HLR_SSAP_Provider_Abort

SSAP Provider Abort associated with the HLR

In the network hierarchy, the immediate parent of the HLR_SSAP_Provider_Abort object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_SSAP_Provider_Abort.YSSAPHSPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR_SSAP_Provider_AbortY"GT:" & SSAPHSPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
HLRThe HLR to which the HLR_SSAP_Provider_Abort belongs.YSSAPHSPA.HLR_id
NetworkNetwork associated with the HLR_SSAP_Provider_Abort.YSSAPHSPA.Network_Id
RegionRegion associated with the HLR_SSAP_Provider_Abort.YSSAPHSPA.Region_Id
Configuration Attributes
NameA user friendly name for the HLR_SSAP_Provider_Abort. SSAPHSPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
HLR_Destination_TypeThe Destination Type of the HLR_SSAP_Provider_Abort SSAPHSPA."GT"
Provider_AbortProvider_Abort associated with the HLR_SSAP_Provider_Abort SSAPHSPA.PA_Id
TechnologyTechnology of the HLR_SSAP_Provider_Abort SSAPHSPA."GSM"
VendorManufacturer of the HLR_SSAP_Provider_Abort SSAPHSPA."Nokia"
VersionSoftware Version of the HLR_SSAP_Provider_Abort "M14.1"


HLR_TCAP_Provider_Abort

TCAP Provider Abort associated with the HLR

In the network hierarchy, the immediate parent of the HLR_TCAP_Provider_Abort object is HLR_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the HLR_TCAP_Provider_Abort.YIACOHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IACIHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACIHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IACOHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
Relationship Attributes
HLR_DestinationThe Destination Id of the HLR_TCAP_Provider_AbortY"GT:" & IACIHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
HLRThe HLR to which the HLR_TCAP_Provider_Abort belongs.YIACIHDPA.HLR_id or IACIHSPA.HLR_id
NetworkNetwork associated with the HLR_TCAP_Provider_Abort.YIACIHDPA.Network_Id or IACIHSPA.Network_Id
RegionRegion associated with the HLR_TCAP_Provider_Abort.YIACIHDPA.Region_Id or IACIHSPA.Region_Id
Configuration Attributes
NameA user friendly name for the HLR_TCAP_Provider_Abort. IACOHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IACIHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACIHSPA.HLR_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IACOHDPA.HLR_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
HLR_Destination_TypeThe Destination Type of the HLR_TCAP_Provider_Abort IACIHDPA."GT" or IACIHSPA."SPC"
Provider_AbortProvider_Abort associated with the HLR_TCAP_Provider_Abort IACIHDPA.PA_Id or IACIHSPA.PA_Id
TechnologyTechnology of the HLR_TCAP_Provider_Abort IACIHDPA."GSM"
VendorManufacturer of the HLR_TCAP_Provider_Abort IACIHDPA."Nokia"
VersionSoftware Version of the HLR_TCAP_Provider_Abort "M14.1"


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.YACHHLR.hlr_id or ACHDEST.hlr_id
Relationship Attributes
RegionRegion associated with the HLR.YACHHLR.Region_Id or ACHDEST.Network_Id
NetworkNetwork associated with the HLR.YACHHLR.Network_Id or ACHDEST.Network_Id
Configuration Attributes
NameA user friendly name preferably unique for the HLR. ACHHLR.hlr_id or ACHDEST.hlr_id
VendorManufacturer of the HLR. "Nokia"
HLR_VersionHardware/Software version of the HLR. "M14.1"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


Interface_LAN

LAN Interface

In the network hierarchy, the immediate parent of the Interface_LAN object is PIU.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Interface_LANYMLANHUTI.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANHUTI.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANHUTI.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANSTIF.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANSTIF.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANSTIF.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANHUEI.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANSEIF.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANHUEI.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANSEIF.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANHUEI.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANSEIF.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id
Relationship Attributes
NetworkNetwork associated with the Interface_LAN.YMLANHUTI.Network_id or HLANHUTI.Network_id or CLANHUTI.Network_id or MLANSTIF.Network_id or HLANSTIF.Network_id or CLANSTIF.Network_id
PIUPIU associated with the Interface_LAN.YMLANHUTI.MSC_id & "/" & UNIT_id & "/" & PIU_id or HLANHUTI.HLR_id & "/" & UNIT_id & "/" & PIU_id or CLANHUTI.CDS_id & "/" & UNIT_id & "/" & PIU_id or MLANSTIF.MSC_id & "/" & UNIT_id & "/" & PIU_id or HLANSTIF.HLR_id & "/" & UNIT_id & "/" & PIU_id or CLANSTIF.CDS_id & "/" & UNIT_id & "/" & PIU_id
RegionRegion associated with the Interface_LAN.YMLANHUTI.Region_id or HLANHUTI.Region_id or CLANHUTI.Region_id or MLANSTIF.Region_id or HLANSTIF.Region_id or CLANSTIF.Region_id
UnitUnit associated with the Interface_LAN.YMLANHUTI.MSC_id & "/" & UNIT_id or HLANHUTI.HLR_id & "/" & UNIT_id or CLANHUTI.CDS_id & "/" & UNIT_id or MLANSTIF.MSC_id & "/" & UNIT_id or HLANSTIF.HLR_id & "/" & UNIT_id or CLANSTIF.CDS_id & "/" & UNIT_id
Configuration Attributes
NameA user friendly name for the Interface_LAN. MLANHUTI.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANHUTI.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANHUTI.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANSTIF.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANSTIF.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANSTIF.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANHUEI.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or CLANSEIF.CDS_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANHUEI.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or HLANSEIF.HLR_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANHUEI.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id or MLANSEIF.MSC_id & "/" & UNIT_id & "/" & PIU_id & "/" & LIF_id
Conn_unitConnection Unit Index of the Interface LAN. MLANHUTI.M289B2C4 or HLANHUTI.M289B2C4 or CLANHUTI.M289B2C4 or MLANSTIF.M288B2C4 or HLANSTIF.M288B2C4 or CLANSTIF.M288B2C4
Conn_unit_indexConnection Unit of the Interface LAN MLANHUTI.M289B2C3 or HLANHUTI.M289B2C3 or CLANHUTI.M289B2C3 or MLANSTIF.M288B2C3 or HLANSTIF.M288B2C3 or CLANSTIF.M288B2C3
Link_typeLink Type of the Interface Lan MLANHUTI.M289B2C2 or HLANHUTI.M289B2C2 or CLANHUTI.M289B2C2 or MLANSTIF.M288B2C2 or HLANSTIF.M288B2C2 or CLANSTIF.M288B2C2
Node_IdNode associated with the Interface_LAN. MLANHUTI.MSC_id or HLANHUTI.HLR_id or CLANHUTI.CDS_id or MLANSTIF.MSC_id or HLANSTIF.HLR_id or CLANSTIF.CDS_id
Node_TypeThe Node Type of the Interface_LAN MLANHUTI."MSC" or HLANHUTI."HLR" or CLANHUTI."CDS" or MLANSTIF."MSC" or HLANSTIF."HLR" or CLANSTIF."CDS"
TechnologyTechnology of the Interface_LAN MLANHUTI."GSM"
VendorManufacturer of the Interface_LAN MLANHUTI."Nokia"
VersionSoftware Version of the Interface_LAN "M14.1"


Interface_MAP

MAP Interface

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Interface_MAPYMAPMDEST.MSC_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHSN.HLR_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHNETI.HLR_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id or MAPMNETI.MSC_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id or MAPMSN.MSC_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHDTRC.HLR_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHSNRC.HLR_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTRC.MSC_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMSNRC.MSC_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHDEST.HLR_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIRC.HLR_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id
Relationship Attributes
NetworkNetwork associated with the Interface_MAP.YMAPMDEST.Network_Id or MAPHSN.Network_Id or MAPHNETI.Network_Id or MAPMNETI.Network_Id or MAPMSN.Network_Id or MAPHDTRC.Network_Id or MAPHSNRC.Network_Id or MAPMDTRC.Network_Id or MAPMSNRC.Network_Id
RegionRegion associated with the Interface_MAP.YMAPMDEST.Region_id or MAPHSN.Region_id or MAPHNETI.Region_id or MAPMNETI.Region_id or MAPMSN.Region_id or MAPHDTRC.Region_id or MAPHSNRC.Region_id or MAPMDTRC.Region_id or MAPMSNRC.Region_id
Configuration Attributes
NameA user friendly name for the Interface_MAP. MAPMDEST.MSC_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHSN.HLR_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHNETI.HLR_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id or MAPMNETI.MSC_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id or MAPMSN.MSC_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHDTRC.HLR_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHSNRC.HLR_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTRC.MSC_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMSNRC.MSC_id & "/" & MIF_Id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPHDEST.HLR_id & "/" & MIF_Id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIRC.HLR_id & "/" & MIF_Id & "/" & NIMSI_id & "/" & SUB_id
Node_IdNode associated with the Interface_MAP. MAPMDEST.MSC_id or MAPHSN.HLR_id or MAPHNETI.HLR_id or MAPMNETI.MSC_id or MAPMSN.MSC_id or MAPHDTRC.HLR_id or MAPHSNRC.HLR_id or MAPMDTRC.MSC_id or MAPMSNRC.MSC_id
Node_TypeThe Node Type of the Interface_MAP MAPMDEST."MSC" or MAPHSN."HLR" or MAPHNETI."HLR" or MAPMNETI."MSC" or MAPMSN."MSC" or MAPHDTRC."HLR" or MAPHSNRC."HLR" or MAPMDTRC."MSC" or MAPMSNRC."MSC"
TechnologyTechnology of the Interface_MAP MAPMDEST."GSM"
VendorManufacturer of the Interface_MAP MAPMDEST."Nokia"
VersionSoftware Version of the Interface_MAP "M14.1"


LAC_Access_Type

Access Type associated with the LAC

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the LAC_Access_Type.YLULAC.MSC_id & "/" & LAC_id & "/" & ACCESS_id
Relationship Attributes
LACThe LAC identifier of the LAC_Access_TypeYLULAC.MSC_id & "-" & LAC_id
MSCThe MSC to which the LAC_Access_Type belongs.YLULAC.MSC_id
NetworkNetwork associated with the LAC_Access_Type.YLULAC.Network_Id
RegionRegion associated with the LAC_Access_Typee.YLULAC.Region_Id
Configuration Attributes
NameA user friendly name for the LAC_Access_Type. LULAC.MSC_id & "/" & LAC_id & "/" & ACCESS_id
TechnologyTechnology of the LAC_Access_Type LULAC."GSM"
VendorManufacturer of the LAC_Access_Type LULAC."Nokia"
VersionSoftware Version of the LAC_Access_Type "M14.1"


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


MAP_Application_Context

MAP Application Context

In the network hierarchy, the immediate parent of the MAP_Application_Context object is Interface_MAP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MAP_Application_ContextYMAPHDTAC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or MAPHNIAC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & AC_id or MAPHSNAC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or MAPMDTAC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or MAPMNIAC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & AC_id or MAPMSNAC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
Relationship Attributes
Interface_MAPThe Interface_MAP of the MAP_Application_ContextYMAPHDTAC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIAC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPHSNAC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTAC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMNIAC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPMSNAC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
NetworkNetwork associated with the MAP_Application_Context.YMAPHDTAC.Network_Id or MAPHNIAC.Network_Id or MAPHSNAC.Network_Id or MAPMDTAC.Network_Id or MAPMNIAC.Network_Id or MAPMSNAC.Network_Id
RegionRegion associated with the MAP_Application_Context.YMAPHDTAC.Region_Id or MAPHNIAC.Region_id or MAPHSNAC.Region_id or MAPMDTAC.Region_id or MAPMNIAC.Region_id or MAPMSNAC.Region_id
Configuration Attributes
NameA user friendly name for the MAP_Application_Context. MAPHDTAC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or MAPHNIAC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & AC_id or MAPHSNAC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or MAPMDTAC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or MAPMNIAC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & AC_id or MAPMSNAC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
Application_ContextApplication Context associated with the MAP_Application_Context MAPHDTAC.AC_id or MAPHNIAC.AC_id or MAPHSNAC.AC_id or MAPMDTAC.AC_id or MAPMNIAC.AC_id or MAPMSNAC.AC_id
Node_IdThe Node identifier of the MAP_Application_Context MAPHDTAC.HLR_id or MAPHNIAC.HLR_id or MAPHSNAC.HLR_id or MAPMDTAC.MSC_id or MAPMNIAC.MSC_id or MAPMSNAC.MSC_id
Node_TypeThe Node Type of the MAP_Application_Context MAPHDTAC."HLR" or MAPHNIAC."HLR" or MAPHSNAC."HLR" or MAPMDTAC."MSC" or MAPMNIAC."MSC" or MAPMSNAC."MSC"
TechnologyTechnology of the MAP_Application_Context MAPHDTAC."GSM"
VendorManufacturer of the MAP_Application_Context MAPHDTAC."Nokia"
VersionSoftware Version of the MAP_Application_Context "M14.1"


MAP_Error_Code

MAP Error Code

In the network hierarchy, the immediate parent of the MAP_Error_Code object is Interface_MAP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MAP Error CodeYMAPHDTEC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPHNIEC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPHSNEC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMDTEC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMNIEC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMSNEC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id
Relationship Attributes
Interface_MAPThe Interface_MAP of the MAP_Error_CodeYMAPHDTEC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIEC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPHSNEC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTEC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMNIEC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPMSNEC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
NetworkNetwork associated with the MAP_Error_Code.YMAPHDTEC.Network_Id or MAPHNIEC.Network_Id or MAPHSNEC.Network_Id or MAPMDTEC.Network_Id or MAPMNIEC.Network_Id or MAPMSNEC.Network_Id
RegionRegion associated with the MAP_Error_Code.YMAPHDTEC.Region_Id or MAPHNIEC.Region_id or MAPHSNEC.Region_id or MAPMDTEC.Region_id or MAPMNIEC.Region_id or MAPMSNEC.Region_id
Configuration Attributes
NameA user friendly name for the MAP_Error_Code. MAPHDTEC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPHNIEC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPHSNEC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMDTEC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMNIEC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id or MAPMSNEC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & EC_id & "/" & VER_id
Error_CodeError Code associated with the MAP_Error_Code MAPHDTEC.EC_id & "/" & VER_id or MAPHNIEC.EC_id & "/" & VER_id or MAPHSNEC.EC_id & "/" & VER_id or MAPMDTEC.EC_id & "/" & VER_id or MAPMNIEC.EC_id & "/" & VER_id or MAPMSNEC.EC_id & "/" & VER_id
Node_IdThe Node identifier of the MAP_Error_Code MAPHDTEC.HLR_id or MAPHNIEC.HLR_id or MAPHSNEC.HLR_id or MAPMDTEC.MSC_id or MAPMNIEC.MSC_id or MAPMSNEC.MSC_id
Node_TypeThe Node Type of the MAP_Error_Code MAPHDTEC."HLR" or MAPHNIEC."HLR" or MAPHSNEC."HLR" or MAPMDTEC."MSC" or MAPMNIEC."MSC" or MAPMSNEC."MSC"
TechnologyTechnology of the MAP_Error_Code MAPHDTEC."GSM"
VendorManufacturer of the MAP_Error_Code MAPHDTEC."Nokia"
VersionSoftware Version of the MAP_Error_Code "M14.1"


MAP_Operation_Code

MAP Operation code

In the network hierarchy, the immediate parent of the MAP_Operation_Code object is Interface_MAP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MAP_Operation_CodeYMAPHDTOC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or MAPHNIOC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & OC_id or MAPHSNOC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or MAPMDTOC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or MAPMNIOC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & OC_id or MAPMSNOC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
Relationship Attributes
Interface_MAPThe Interface_MAP of the MAP_Operation_CodeYMAPHDTOC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIOC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPHSNOC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTOC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMNIOC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPMSNOC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
NetworkNetwork associated with the MAP_Operation_Code.YMAPHDTOC.Network_Id or MAPHNIOC.Network_Id or MAPHSNOC.Network_Id or MAPMDTOC.Network_Id or MAPMNIOC.Network_Id or MAPMSNOC.Network_Id
RegionRegion associated with the MAP_Operation_Code.YMAPHDTOC.Region_Id or MAPHNIOC.Region_id or MAPHSNOC.Region_id or MAPMDTOC.Region_id or MAPMNIOC.Region_id or MAPMSNOC.Region_id
Configuration Attributes
NameA user friendly name for the MAP_Operation_Code. MAPHDTOC.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or MAPHNIOC.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & OC_id or MAPHSNOC.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or MAPMDTOC.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or MAPMNIOC.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & OC_id or MAPMSNOC.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
Node_IdThe Node identifier of the MAP_Operation_Code MAPHDTOC.HLR_id or MAPHNIOC.HLR_id or MAPHSNOC.HLR_id or MAPMDTOC.MSC_id or MAPMNIOC.MSC_id or MAPMSNOC.MSC_id
Node_TypeThe Node Type of the MAP_Operation_Code MAPHDTOC."HLR" or MAPHNIOC."HLR" or MAPHSNOC."HLR" or MAPMDTOC."MSC" or MAPMNIOC."MSC" or MAPMSNOC."MSC"
Operation_CodeOperation_Code associated with the MAP_Operation_Code MAPHDTOC.OC_id or MAPHNIOC.OC_id or MAPHSNOC.OC_id or MAPMDTOC.OC_id or MAPMNIOC.OC_id or MAPMSNOC.OC_id
TechnologyTechnology of the MAP_Operation_Code MAPHDTOC."GSM"
VendorManufacturer of the MAP_Operation_Code MAPHDTOC."Nokia"
VersionSoftware Version of the MAP_Operation_Code "M14.1"


MAP_Provider_Abort

MAP Provider Abort

In the network hierarchy, the immediate parent of the MAP_Provider_Abort object is Interface_MAP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MAP_Provider_AbortYMAPHDTPA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_id or MAPHNIPA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & PA_id or MAPHSNPA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_id or MAPMDTPA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_id or MAPMNIPA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & PA_id or MAPMSNPA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_id
Relationship Attributes
Interface_MAPThe Interface_MAP of the MAP_Provider_AbortYMAPHDTPA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIPA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPHSNPA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTPA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMNIPA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPMSNPA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
NetworkNetwork associated with the MAP_Provider_Abort.YMAPHDTPA.Network_Id or MAPHNIPA.Network_Id or MAPHSNPA.Network_Id or MAPMDTPA.Network_Id or MAPMNIPA.Network_Id or MAPMSNPA.Network_Id
RegionRegion associated with the MAP_Provider_Abort.YMAPHDTPA.Region_Id or MAPHNIPA.Region_id or MAPHSNPA.Region_id or MAPMDTPA.Region_id or MAPMNIPA.Region_id or MAPMSNPA.Region_id
Configuration Attributes
NameA user friendly name for the MAP_Provider_Abort. MAPHDTPA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_id or MAPHNIPA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & PA_id or MAPHSNPA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_id or MAPMDTPA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_id or MAPMNIPA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & PA_id or MAPMSNPA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_id
Node_IdThe Node identifier of the MAP_Provider_Abort MAPHDTPA.HLR_id or MAPHNIPA.HLR_id or MAPHSNPA.HLR_id or MAPMDTPA.MSC_id or MAPMNIPA.MSC_id or MAPMSNPA.MSC_id
Node_TypeThe Node Type of the MAP_Provider_Abort MAPHDTPA."HLR" or MAPHNIPA."HLR" or MAPHSNPA."HLR" or MAPMDTPA."MSC" or MAPMNIPA."MSC" or MAPMSNPA."MSC"
Provider_AbortProvider Abort associated with the MAP_Provider_Abort MAPHDTPA.PA_id or MAPHNIPA.PA_id or MAPHSNPA.PA_id or MAPMDTPA.PA_id or MAPMNIPA.PA_id or MAPMSNPA.PA_id
TechnologyTechnology of the MAP_Provider_Abort MAPHDTPA."GSM"
VendorManufacturer of the MAP_Provider_Abort MAPHDTPA."Nokia"
VersionSoftware Version of the MAP_Provider_Abort "M14.1"


MAP_User_Abort

MAP User Abort

In the network hierarchy, the immediate parent of the MAP_User_Abort object is Interface_MAP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MAP_User_AbortYMAPHDTUA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & UA_id or MAPHNIUA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & UA_id or MAPHSNUA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & UA_id or MAPMDTUA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & UA_id or MAPMNIUA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & UA_id or MAPMSNUA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & UA_id
Relationship Attributes
Interface_MAPThe Interface_MAP of the MAP_User_AbortYMAPHDTUA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPHNIUA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPHSNUA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or MAPMDTUA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or MAPMNIUA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id or MAPMSNUA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
NetworkNetwork associated with the MAP_User_Abort.YMAPHDTUA.Network_Id or MAPHNIUA.Network_Id or MAPHSNUA.Network_Id or MAPMDTUA.Network_Id or MAPMNIUA.Network_Id or MAPMSNUA.Network_Id
RegionRegion associated with the MAP_User_Abort.YMAPHDTUA.Region_Id or MAPHNIUA.Region_id or MAPHSNUA.Region_id or MAPMDTUA.Region_id or MAPMNIUA.Region_id or MAPMSNUA.Region_id
Configuration Attributes
NameA user friendly name for the MAP_User_Abort. MAPHDTUA.HLR_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & UA_id or MAPHNIUA.HLR_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & UA_id or MAPHSNUA.HLR_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & UA_id or MAPMDTUA.MSC_id & "/" & MIF_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & UA_id or MAPMNIUA.MSC_id & "/" & MIF_id & "/" & NIMSI_id & "/" & SUB_id & "/" & UA_id or MAPMSNUA.MSC_id & "/" & MIF_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & UA_id
Node_IdThe Node identifier of the MAP_User_Abort MAPHDTUA.HLR_id or MAPHNIUA.HLR_id or MAPHSNUA.HLR_id or MAPMDTUA.MSC_id or MAPMNIUA.MSC_id or MAPMSNUA.MSC_id
Node_TypeThe Node Type of the MAP_User_Abort MAPHDTUA."HLR" or MAPHNIUA."HLR" or MAPHSNUA."HLR" or MAPMDTUA."MSC" or MAPMNIUA."MSC" or MAPMSNUA."MSC"
TechnologyTechnology of the MAP_User_Abort MAPHDTUA."GSM"
User_AbortUser Abort associated with the MAP_User_Abort MAPHDTUA.UA_id or MAPHNIUA.UA_id or MAPHSNUA.UA_id or MAPMDTUA.UA_id or MAPMNIUA.UA_id or MAPMSNUA.UA_id
VendorManufacturer of the MAP_User_Abort MAPHDTUA."Nokia"
VersionSoftware Version of the MAP_User_Abort "M14.1"


MGW_Neighbour

MGW neighbour relationships

In the network hierarchy, the immediate parent of the MGW_Neighbour object is MGW.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the MGW_NeighbourYSMGW.msc_id & "-" & mgwm_id & "-" & nmgwm_id
Relationship Attributes
Source_MGWThe source MGW identifierYSMGW.mgwmname_id
RegionIdentifier of the RegionYSMGW.Region_Id
NetworkIdentifier of the NetworkYSMGW.Network_Id
Configuration Attributes
NameA user-friendly name for the MGW_Neighbour SMGW.lookup("nc_msc","msc_name",utime(startDate & startTime,"%Y-%m-%d %R"),msc_id) & "-" & mgwmname_id & "-" & nmgwm_id
Target_MGW_IdThe target MGW identifier SMGW.nmgwm_id


MGW

Media Gateway network element used to modify speech, data and protocols in the connectivity layer.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MGW.YMEG.mgwmname_id OR IPATM.mgwmname_id&"-"&nmgwname_id or CRCDT.mgwmname_id or MGWTCP.PMGW_ID or MGWTCV.PMGW_ID or SIMCMGW.PMGW_ID or CRTERM.mgwmname_id or EVEM.mgwmname_id or NMGW.mgwmname_id or UPD.mgwmname_id
Relationship Attributes
NetworkNetwork associated with the MGW.YMEG.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or CRCDT.lookup("nc_cds","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),cds_id) or MGWTCV.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or MGWTCP.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or SIMCMGW.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or CRTERM.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or EVEM.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or NMGW.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or UPD.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or IPATM.lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
RegionRegion associated with the MGW.YMEG.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or CRCDT.lookup("nc_cds","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),cds_id) or MGWTCV.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or MGWTCP.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or SIMCMGW.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or CRTERM.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or EVEM.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or NMGW.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or UPD.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id) or IPATM.lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the MGW. MEG.mgwmname_id OR IPATM.mgwmname_id&"-"&nmgwname_id or CRCDT.mgwmname_id or MGWTCP.PMGW_ID or MGWTCV.PMGW_ID or SIMCMGW.PMGW_ID or CRTERM.mgwmname_id or EVEM.mgwmname_id or NMGW.mgwmname_id or UPD.mgwmname_id
MGW_TypeType of MGW. "Populated by the customer"
MGW_VersionHardware/Software version of the MGW. "Populated by the customer"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "Populated by the customer"
VendorManufacturer of the MGW. "Populated by the customer"


MSC_CAP_Application_Context

CAP Application Context associated with the MSC

In the network hierarchy, the immediate parent of the MSC_CAP_Application_Context object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_CAP_Application_ContextYCAPMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or CAPMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
Relationship Attributes
MSC_DestinationThe MSC_Destination Id of the MSC_CAP_Application_ContextY"GT:" & CAPMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSCMSC associated with the MSC_CAP_Application_ContextYCAPMDAC.MSC_id or CAPMSAC.MSC_id
NetworkNetwork associated with the MSC_CAP_Application_Context.YCAPMDAC.Network_id or CAPMSAC.Network_id
RegionRegion associated with the MSC_CAP_Application_Context.YCAPMDAC.Region_id or CAPMSAC.Region_id
Configuration Attributes
NameA user friendly name for the MSC_CAP_Application_Context. CAPMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or CAPMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
TechnologyTechnology of the MSC_CAP_Application_Context CAPMDAC."GSM"
VendorManufacturer of the MSC_CAP_Application_Context CAPMDAC."Nokia"
VersionSoftware Version of the MSC_CAP_Application_Context "M14.1"


MSC_Destination

Destination associated with the MSC

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_DestinationY"GT:" & IDPMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACIMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & SSAPMSUB.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & CAPMSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IACOMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC1MSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2MSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2MSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOMSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & CAPMDEST.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC1MDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2MDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IACOMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
Relationship Attributes
MSCMSC associated with the MSC_DestinationYIDPMDES.MSC_id or IDPMSN.MSC_id or IACIMDES.MSC_id or IACIMSN.MSC_id or SSAPMSUB.MSC_id or CAPMSN.MSC_id or CAPMSRC.MSC_id or IACOMSN.MSC_id or IOC1MSN.MSC_id or IOC2MSN.MSC_id or IOC2MSRC.MSC_id or IOCOMSN.MSC_id or IOCOMSRC.MSC_id or CAPMDEST.MSC_id or IOC1MDES.MSC_id or IOC2MDES.MSC_id or IACOMDES.MSC_id or IOCOMDES.MSC_id
NetworkNetwork associated with the MSC_Destination.YIDPMDES.Network_id or IDPMSN.Network_id or IACIMDES.Network_id or IACIMSN.Network_id or SSAPMSUB.Network_id
RegionRegion associated with the MSC_Destination.YIDPMDES.Region_id or IDPMSN.Region_id or IACIMDES.Region_id or IACIMSN.Region_id or SSAPMSUB.Region_id
Configuration Attributes
NameA user friendly name for the MSC_Destination. "GT:" & IDPMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACIMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & SSAPMSUB.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & CAPMSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IACOMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC1MSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2MSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOC2MSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOMSN.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & IOCOMSRC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & CAPMDEST.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC1MDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOC2MDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IACOMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "GT:" & IOCOMDES.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
TechnologyTechnology of the MSC_Destination IDPMDES."GSM"
VendorManufacturer of the MSC_Destination IDPMDES."Nokia"
VersionSoftware Version of the MSC_Destination "M14.1"


MSC_Detection_Point

Detection Point associated with the MSC

In the network hierarchy, the immediate parent of the MSC_Detection_Point object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the CAP Error CodeYIDPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id or IDPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id or CAPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id or CAPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_Detection_PointY"GT:" & IDPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IDPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "SPC:" & CAPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & CAPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
MSCThe MSC to which the MSC_Detection_Point belongs.YIDPMD.MSC_id or IDPMS.MSC_id or CAPMS.MSC_id or CAPMD.MSC_id
NetworkNetwork associated with the MSC_Detection_Point.YIDPMD.Network_Id or IDPMS.Network_Id or CAPMS.Network_Id or CAPMD.Network_Id
RegionRegion associated with the MSC_Detection_Point.YIDPMD.Region_Id or IDPMS.Region_Id or CAPMS.Region_Id or CAPMD.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_Detection_Point. IDPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id or IDPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id or CAPMS.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & DP_id or CAPMD.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DP_id
Detection_PointDetection Point associated with the MSC_Detection_Point IDPMD.DP_id or IDPMS.DP_id or CAPMS.DP_id or CAPMD.DP_id
MSC_Destination_TypeThe Destination Type of the MSC_Detection_Point IDPMD."GT" or CAPMS."SPC" or IDPMS."SPC" or CAPMD."GT"
TechnologyTechnology of the MSC_Detection_Point IDPMD."GSM"
VendorManufacturer of the MSC_Detection_Point IDPMD."Nokia"
VersionSoftware Version of the MSC_Detection_Point "M14.1"


MSC_INAP_Application_Context

INAP Application Context associated with the MSC

In the network hierarchy, the immediate parent of the MSC_INAP_Application_Context object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_INAP_Application_ContextYIACIMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACIMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or IACOMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACOMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
Relationship Attributes
MSC_DestinationThe MSC_Destination Id of the MSC_INAP_Application_ContextY"GT:" & IACIMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & IACOMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACOMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSCMSC associated with the MSC_INAP_Application_ContextYIACIMDAC.MSC_id or IACIMSAC.MSC_id or IACOMDAC.MSC_id or IACOMSAC.MSC_id
NetworkNetwork associated with the MSC_INAP_Application_Context.YIACIMDAC.Network_id or IACIMSAC.Network_id or IACOMDAC.Network_id or IACOMSAC.Network_id
RegionRegion associated with the MSC_INAP_Application_Context.YIACIMDAC.Region_id or IACIMSAC.Region_id or IACOMDAC.Region_id or IACOMSAC.Region_id
Configuration Attributes
NameA user friendly name for the MSC_INAP_Application_Context. IACIMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACIMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id or IACOMDAC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & AC_id or IACOMSAC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & AC_id
TechnologyTechnology of the MSC_INAP_Application_Context IACIMDAC."GSM"
VendorManufacturer of the MSC_INAP_Application_Context IACIMDAC."Nokia"
VersionSoftware Version of the MSC_INAP_Application_Context "M14.1"


MSC_INAP_Error_Code

INAP Error Code associated with the MSC

In the network hierarchy, the immediate parent of the MSC_INAP_Error_Code object is MSC_INAP_Op_Code.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_INAP_Error_Code.YIOC1MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC1MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC2MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOCOMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_INAP_Error_CodeY"GT:" & IOC1MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSC_INAP_Op_CodeThe Operation Code Id of the MSC_INAP_Error_CodeYIOC1MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
MSCThe MSC to which the MSC_INAP_Error_Code belongs.YIOC1MDEC.MSC_id or IOC1MSEC.MSC_id
NetworkNetwork associated with the MSC_INAP_Error_Code.YIOC1MDEC.Network_Id or IOC1MSEC.Network_Id
RegionRegion associated with the MSC_INAP_Error_Code.YIOC1MDEC.Region_Id or IOC1MSEC.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_INAP_Error_Code. IOC1MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC1MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOC2MSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOCOMSEC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or IOC2MDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id or IOCOMDEC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id & "/" & EC_id
ErrorCodeError Code associated with the MSC_INAP_Error_Code IOC1MDEC.EC_id or IOC1MSEC.EC_id
MSC_Destination_TypeThe Destination Type of the MSC_INAP_Error_Code IOC1MDEC."GT" or IOC1MSEC."SPC"
TechnologyTechnology of the MSC_INAP_Error_Code IOC1MDEC."GSM"
VendorManufacturer of the MSC_INAP_Error_Code IOC1MDEC."Nokia"
VersionSoftware Version of the MSC_INAP_Error_Code "M14.1"


MSC_INAP_Op_Code

INAP Operation Code associated with the MSC

In the network hierarchy, the immediate parent of the MSC_INAP_Op_Code object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_INAP_Op_Code.YIOC1MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOC2MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOCOMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC2MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOCOMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_INAP_Op_CodeY"GT:" & IOC1MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IOC1MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSCThe MSC to which the MSC_INAP_Op_Code belongs.YIOC1MDOC.MSC_id or IOC1MSOC.MSC_id
NetworkNetwork associated with the MSC_INAP_Op_Code.YIOC1MDOC.Network_Id or IOC1MSOC.Network_Id
RegionRegion associated with the MSC_INAP_Op_Code.YIOC1MDOC.Region_Id or IOC1MSOC.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_INAP_Op_Code. IOC1MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC1MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOC2MDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOCOMDOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_id or IOC2MSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id or IOCOMSOC.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & OC_id
MSC_Destination_TypeThe Destination Type of the MSC_INAP_Op_Code IOC1MDOC."GT" or IOC1MSOC."SPC"
OpCodeOperation Code associated with the MSC_INAP_Op_Code IOC1MDOC.OC_id or IOC1MSOC.OC_id
TechnologyTechnology of the MSC_INAP_Op_Code IOC1MDOC."GSM"
VendorManufacturer of the MSC_INAP_Op_Code IOC1MDOC."Nokia"
VersionSoftware Version of the MSC_INAP_Op_Code "M14.1"


MSC_SSAP_Dialogue

SSAP Dialogue associated with the MSC

In the network hierarchy, the immediate parent of the MSC_SSAP_Dialogue object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_SSAP_Dialogue.YSSAPMSDI.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DI_Id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_SSAP_DialogueY"GT:" & SSAPMSDI.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
MSCThe MSC to which the MSC_SSAP_Dialogue belongs.YSSAPMSDI.MSC_id
NetworkNetwork associated with the MSC_SSAP_Dialogue.YSSAPMSDI.Network_Id
RegionRegion associated with the MSC_SSAP_Dialogue.YSSAPMSDI.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_SSAP_Dialogue. SSAPMSDI.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & DI_Id
DialogueDialogue associated with the MSC_SSAP_Dialogue SSAPMSDI.DI_Id
MSC_Destination_TypeThe Destination Type of the MSC_SSAP_Dialogue SSAPMSDI."GT"
TechnologyTechnology of the MSC_SSAP_Dialogue SSAPMSDI."GSM"
VendorManufacturer of the MSC_SSAP_Dialogue SSAPMSDI."Nokia"
VersionSoftware Version of the MSC_SSAP_Dialogue "M14.1"


MSC_SSAP_Operation

SSAP Operation code associated with the MSC

In the network hierarchy, the immediate parent of the MSC_SSAP_Operation object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_SSAP_Operation code.YSSAPMSOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_Id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_SSAP_OperationY"GT:" & SSAPMSOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
MSCThe MSC to which the MSC_SSAP_Operation belongs.YSSAPMSOC.MSC_id
NetworkNetwork associated with the MSC_SSAP_Operation.YSSAPMSOC.Network_Id
RegionRegion associated with the MSC_SSAP_Operation.YSSAPMSOC.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_SSAP_Operation code. SSAPMSOC.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & OC_Id
MSC_Destination_TypeThe Destination Type of the MSC_SSAP_Operation SSAPMSOC."GT"
OperationOperation Code associated with the MSC_SSAP_Operation SSAPMSOC.OC_Id
TechnologyTechnology of the MSC_SSAP_Operation SSAPMSOC."GSM"
VendorManufacturer of the MSC_SSAP_Operation SSAPMSOC."Nokia"
VersionSoftware Version of the MSC_SSAP_Operation "M14.1"


MSC_SSAP_Provider_Abort

SSAP Provider Abort associated with the MSC

In the network hierarchy, the immediate parent of the MSC_SSAP_Provider_Abort object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_SSAP_Provider_Abort.YSSAPMSPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_SSAP_Provider_AbortY"GT:" & SSAPMSPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id
MSCThe MSC to which the MSC_SSAP_Provider_Abort belongs.YSSAPMSPA.MSC_id
NetworkNetwork associated with the MSC_SSAP_Provider_Abort.YSSAPMSPA.Network_Id
RegionRegion associated with the MSC_SSAP_Provider_Abort.YSSAPMSPA.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_SSAP_Provider_Abort. SSAPMSPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id
MSC_Destination_TypeThe Destination Type of the MSC_SSAP_Provider_Abort SSAPMSPA."GT"
Provider_AbortProvider_Abort associated with the MSC_SSAP_Provider_Abort SSAPMSPA.PA_Id
TechnologyTechnology of the MSC_SSAP_Provider_Abort SSAPMSPA."GSM"
VendorManufacturer of the MSC_SSAP_Provider_Abort SSAPMSPA."Nokia"
VersionSoftware Version of the MSC_SSAP_Provider_Abort "M14.1"


MSC_TCAP_Provider_Abort

TCAP Provider Abort associated with the MSC

In the network hierarchy, the immediate parent of the MSC_TCAP_Provider_Abort object is MSC_Destination.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC_TCAP_Provider_Abort.YIACIMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACIMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id or CAPMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or CAPMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id or IACOMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACOMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id
Relationship Attributes
MSC_DestinationThe Destination Id of the MSC_TCAP_Provider_AbortY"GT:" & IACIMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & IACIMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id or "GT:" & CAPMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id or "SPC:" & CAPMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id
MSCThe MSC to which the MSC_TCAP_Provider_Abort belongs.YIACIMDPA.MSC_id or IACIMSPA.MSC_id or CAPMDPA.MSC_id or CAPMSPA.MSC_id
NetworkNetwork associated with the MSC_TCAP_Provider_Abort.YIACIMDPA.Network_Id or IACIMSPA.Network_Id or CAPMDPA.Network_Id or CAPMSPA.Network_Id
RegionRegion associated with the MSC_TCAP_Provider_Abort.YIACIMDPA.Region_Id or IACIMSPA.Region_Id or CAPMDPA.Region_Id or CAPMSPA.Region_Id
Configuration Attributes
NameA user friendly name for the MSC_TCAP_Provider_Abort. IACIMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACIMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id or CAPMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or CAPMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id or IACOMDPA.MSC_id & "/" & DESTTYPE_id & "/" & DEST_id & "/" & SUB_id & "/" & PA_Id or IACOMSPA.MSC_id & "/" & SNET_id & "/" & SPC_id & "/" & SPCN_id & "/" & SUB_id & "/" & PA_Id
MSC_Destination_TypeThe Destination Type of the MSC_TCAP_Provider_Abort IACIMDPA."GT" or IACIMSPA."SPC" or CAPMDPA."GT" or CAPMSPA."SPC"
Provider_AbortProvider_Abort associated with the MSC_TCAP_Provider_Abort IACIMDPA.PA_Id or IACIMSPA.PA_Id or CAPMDPA.PA_Id or CAPMSPA.PA_Id
TechnologyTechnology of the MSC_TCAP_Provider_Abort IACIMDPA."GSM"
VendorManufacturer of the MS_TCAPC_Provider_Abort IACIMDPA."Nokia"
VersionSoftware Version of the MSC_TCAP_Provider_Abort "M14.1"


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


Neighbour_BSC

BSC (or RNC) neighbour relationships.

In the network hierarchy, the immediate parent of the Neighbour_BSC object is BSC.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the BSC.YBRC.msc_id &"-"& bscm_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nrncm_id or BS.msc_id &"-"& bscm_id &"-"& nbscm_id or HMRBC1.msc_id &"-"& mccm_id &"-"& mncm_id&"-"& rncm_id&"-"& nbscm_id or HMRRC.msc_id &"-"& rncm_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nrncm_id
Relationship Attributes
Source_BSCA unique identifier for the Source BSC.YBRC.msc_id &"-"& bscm_id or BS.msc_id &"-"& bscm_id or HMRBC1.msc_id &"-"& rncm_id or HMRRC.msc_id &"-"& rncm_id
Configuration Attributes
NameA user friendly name preferably unique for the BSC. BRC.msc_id &"-"& bscm_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nrncm_id or BS.msc_id &"-"& bscm_id &"-"& nbscm_id or HMRBC1.msc_id &"-"& mccm_id &"-"& mncm_id&"-"& rncm_id&"-"& nbscm_id or HMRRC.msc_id &"-"& rncm_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nrncm_id
Target_BSC_IdA unique identifier for the Target BSC. BRC.nmccm_id &"-"& nmncm_id &"-"& nrncm_id or BS.nbscm_id or HMRBC1.nbscm_id or HMRRC.nmccm_id &"-"& nmncm_id &"-"& nrncm_id
Source_BSC_TypeType of Source BSC. BRC."BSC" or BS."BSC" or HMRBC1."RNC" or HMRRC."RNC"
Target_BSC_TypeType of Target BSC. BRC."RNC" or BS."BSC" or HMRBC1."BSC" or HMRRC."RNC"
Source_BSC_VersionHardware/Software version of the Source BSC. "M14.1"
Target_BSC_VersionHardware/Software version of the Target BSC. "M14.1"
Source_BSC_VendorManufacturer of the Source BSC. "Nokia"
Target_BSC_VendorManufacturer of the Target BSC. "Nokia"
Source_BSC_TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Target_BSC_TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


Neighbour

Represents a handover relationship between two cells that may perform handovers to each other.

In the network hierarchy, the immediate parent of the Neighbour object is Cell.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Neighbour.YHO2NCI.msc_id &"-"& lac_id &"-"& ci_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id or HO2NCM.msc_id &"-"& mccm_id &"-"& mncm_id &"-"& lac_id &"-"& ci_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id
Relationship Attributes
Source_CellA unique identifier for the Cell_Id of the Cell that is handling calls.YHO2NCI.msc_id &"-"& lac_id &"-"& ci_id or HO2NCM.msc_id &"-"& lac_id &"-"& ci_id
Configuration Attributes
NameA user friendly name preferably unique for the Neighbour. HO2NCI.msc_id &"-"& lac_id &"-"& ci_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id or HO2NCM.msc_id &"-"& mccm_id &"-"& mncm_id &"-"& lac_id &"-"& ci_id &"-"& nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id
Target_Cell_IdA unique identifier for the Cell_Id of the Cell that is receiving handed-over calls. HO2NCI.nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id or HO2NCM.nmccm_id &"-"& nmncm_id &"-"& nlac_id &"-"& nci_id
Source_Cell_TypeType of Source Cell. "To be defined"
Target_Cell_TypeType of Target Cell. "To be defined"
Source_Cell_VersionHardware/Software version of the Source Cell. "M14.1"
Target_Cell_VersionHardware/Software version of the Target Cell. "M14.1"
Source_Cell_VendorManufacturer of the Source Cell. "Nokia"
Target_Cell_VendorManufacturer of the Target Cell. "Nokia"
Source_Cell_TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Target_Cell_TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Target_Cell_PositionPosition of Target Cell. "Populated by the 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"


PIU

Plug in Unit

In the network hierarchy, the immediate parent of the PIU object is Computer_Unit.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDPrimary identifier of the Plug In Unit(PIU).YMLANSAPI.MSC_id & "/" & Unit_id & "/" & PIU_id or CLANSAPI.CDS_id & "/" & Unit_id & "/" & PIU_id or HLANSAPI.HLR_id & "/" & Unit_id & "/" & PIU_id
Relationship Attributes
Computer_UnitComputer unit of the Plug In unit.YMLANSAPI.MSC_id & "/" & Unit_id or CLANSAPI.CDS_Id & "/" & Unit_id or HLANSAPI.HLR_Id & "/" & Unit_id
NetworkNetwork associated with the Plug In unit.YMLANSAPI.Network_Id or CLANSAPI.Network_Id or HLANSAPI.Network_Id
RegionRegion associated with the Plug In unit.YMLANSAPI.Region_Id or CLANSAPI.Region_Id or HLANSAPI.Region_Id
Configuration Attributes
NameMeaningful name of the Plug In Unit. MLANSAPI.MSC_id & "/" & Unit_id & "/" & PIU_id or CLANSAPI.CDS_id & "/" & Unit_id & "/" & PIU_id or HLANSAPI.HLR_id & "/" & Unit_id & "/" & PIU_id
Node_IdIdentifier of the Node MLANSAPI.MSC_id or CLANSAPI.CDS_id or HLANSAPI.HLR_id
Node_NameMeaningful name of the Node. MLANSAPI.MSC_id or CLANSAPI.CDS_id or HLANSAPI.HLR_id
Node_TypeType of the Node MLANSAPI."MSC" or CLANSAPI."CDS" or HLANSAPI."HLR"
TechnologyTechnology of the node (e.g. UMTS, GPRS). MLANSAPI."GSM"
VersionThe hardware/software version of this Plug In Unit. "M14.1"


PLMN

A Public Land Mobile Network

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the PLMNYPLMNV.plmnname_id
Configuration Attributes
NameA user-friendly name for the PLMN PLMNV.plmnname_id
TechnologyThe Technology (e.g. GSM, UMTS) of this element "GSM"


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.YRESMSC.msc_id&"-"&unit_id OR MBSRR.srr_id&"-"&unit_id OR MBMSC.msc_id&"-"&unit_id OR MBHLR.hlr_id&"-"&unit_id OR UMBMC.cds_id&"-"&unit_id OR ULOAD.cds_id&"-"&unit_id OR CLOM.msc_id&"-"&unit_id OR CLOH.hlr_id&"-"&unit_id OR CLOS.srr_id&"-"&unit_id OR REM.msc_id&"-"&unit_id OR REH.hlr_id&"-"&unit_id OR RES.srr_id&"-"&unit_id OR RESTC.cds_id&"-"&unit_id OR RESHLR.hlr_id&"-"&unit_id OR RESSRR.srr_id&"-"&unit_id OR CDRT.msc_id&"-"&unit_id OR CDR.msc_id&"-"&unit_id OR TCPIP.msc_id&"-"&unit_id OR SIP.msc_id&"-"&unit_id
Relationship Attributes
RegionRegion associated with the Processor.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESMSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MBSRR.srr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MBMSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MBHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UMBMC.cds_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ULOAD.cds_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CLOM.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CLOH.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CLOS.srr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),REM.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),REH.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RES.srr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESTC.cds_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESSRR.srr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CDRT.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CDR.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TCPIP.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SIP.msc_id)
NetworkNetwork associated with the Processor.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESMSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MBSRR.srr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MBMSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MBHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UMBMC.cds_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ULOAD.cds_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CLOM.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CLOH.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CLOS.srr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),REM.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),REH.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RES.srr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESTC.cds_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RESSRR.srr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CDRT.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CDR.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TCPIP.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SIP.msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the Processor. RESMSC.msc_id&"-"&unit_id OR MBSRR.srr_id&"-"&unit_id OR MBMSC.msc_id&"-"&unit_id OR MBHLR.hlr_id&"-"&unit_id OR UMBMC.cds_id&"-"&unit_id OR ULOAD.cds_id&"-"&unit_id OR CLOM.msc_id&"-"&unit_id OR CLOH.hlr_id&"-"&unit_id OR CLOS.srr_id&"-"&unit_id OR REM.msc_id&"-"&unit_id OR REH.hlr_id&"-"&unit_id OR RES.srr_id&"-"&unit_id OR RESTC.cds_id&"-"&unit_id OR RESHLR.hlr_id&"-"&unit_id OR RESSRR.srr_id&"-"&unit_id OR CDRT.msc_id&"-"&unit_id OR CDR.msc_id&"-"&unit_id OR TCPIP.msc_id&"-"&unit_id OR SIP.msc_id&"-"&unit_id
Processor_TypeType of Processor. MBMSC."message_bus" or MBHLR."message_bus" or MBSRR."message_bus" or UMBMC."message_bus" or ULOAD."computer_unit" or CLOM."computer_unit" or CLOH."computer_unit" or CLOS."computer_unit" or REM."signaling_unit" or REH."signaling_unit" or RES."signaling_unit" or RESTC."computer_unit" or RESMSC."control_unit" or RESHLR."control_unit" or RESSRR."control_unit" or CDRT."computer_unit" or CDR."computer_unit" or TCPIP."computer_unit" or SIP."computer_unit"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Node_IdThis is the identifier for the network element containing the Processor. RESMSC.msc_id OR MBSRR.srr_id OR MBMSC.msc_id OR MBHLR.hlr_id OR UMBMC.cds_id OR ULOAD.cds_id OR CLOM.msc_id OR CLOH.hlr_id OR CLOS.srr_id OR REM.msc_id OR REH.hlr_id OR RES.srr_id OR RESTC.cds_id OR RESHLR.hlr_id OR RESSRR.srr_id OR CDRT.msc_id OR CDR.msc_id OR TCPIP.msc_id OR SIP.msc_id
Node_NameA user friendly name preferably unique for the Node. RESMSC.msc_id OR MBSRR.srr_id OR MBMSC.msc_id OR MBHLR.hlr_id OR UMBMC.cds_id OR ULOAD.cds_id OR CLOM.msc_id OR CLOH.hlr_id OR CLOS.srr_id OR REM.msc_id OR REH.hlr_id OR RES.srr_id OR RESTC.cds_id OR RESHLR.hlr_id OR RESSRR.srr_id OR CDRT.msc_id OR CDR.msc_id OR TCPIP.msc_id OR SIP.msc_id
Node_TypeThe type of the network element containing the Processor. RESMSC."MSC" OR MBSRR."SRR" OR MBMSC."MSC" OR MBHLR."HLR" OR UMBMC."CDS" OR ULOAD."CDS" OR CLOM."MSC" OR CLOH."HLR" OR CLOS."SRR" OR REM."MSC" OR REH."HLR" OR RES."SRR" OR RESTC."CDS" OR RESHLR."HLR" OR RESSRR."SRR" OR CDRT."MSC" OR CDR."MSC" OR TCPIP."MSC" OR SIP."MSC"
Processor_VersionHardware/Software version of the Processor. "M14.1"
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


RNC

The Radio Network Controller provides all the control functions and physical links between the MSC (and/or SGSN) and Cell. It switches circuit/packet data & provides functions such as handover, cell configuration data & control of RF power levels in base transceiver stations.

In the network hierarchy, the immediate parent of the RNC object is SGSN.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the RNC.YCSSR.msc_id&"-"&rncm_id or RNCMCC.msc_id&"-"&rncm_id
Relationship Attributes
MSCThe MSC to which this RNC is connected.YCSSR.msc_id OR RNCMCC.msc_id
RegionRegion associated with the RNC.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CSSR.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RNCMCC.msc_id)
NetworkNetwork associated with the RNC.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CSSR.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),RNCMCC.msc_id)
SGSNA unique identifier for the SGSN.Y"No mapping"
Configuration Attributes
NameA user friendly name preferably unique for the RNC. CSSR.msc_id&"-"&rncm_id or RNCMCC.msc_id&"-"&rncm_id
VendorManufacturer of the RNC. "Nokia"
RNC_VersionHardware/Software version of the RNC. "M14.1"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


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 or CGRCC.msc_id&"/"&cgr_id or CGRC.cds_id&"/"&cgr_id or CSTSC.msc_id&"/"&cgr_id or CTD.msc_id&"/"&cgr_id or LOADM.msc_id&"/"&cgr_id or PRCAR.msc_id&"/"&route_id or ROU.msc_id&"/"&dest_id&"/"&subdest_id&"/"&route_id or ROUTDM.msc_id&"/"&dest_id&"/"&alt_id&"/"&dtype_id&"/"&did_id&"/"&dmode_id
Relationship Attributes
RegionRegion associated with the Route IF.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CGR.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CGRCC.msc_id) or lookup("nc_cds","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CGRC.cds_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CSTSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CTD.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),LOADM.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),PRCAR.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ROU.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ROUTDM.msc_id)
NetworkNetwork associated with the Route IF.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CGR.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CGRCC.msc_id) or lookup("nc_cds","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CGRC.cds_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CSTSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CTD.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),LOADM.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),PRCAR.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ROU.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),ROUTDM.msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the Route IF. CGR.msc_id&"/"&cgr_id or CGRCC.msc_id&"/"&cgr_id or CGRC.cds_id&"/"&cgr_id or CSTSC.msc_id&"/"&cgr_id or CTD.msc_id&"/"&cgr_id or LOADM.msc_id&"/"&cgr_id or PRCAR.msc_id&"/"&route_id or ROU.msc_id&"/"&dest_id&"/"&subdest_id&"/"&route_id or ROUTDM.msc_id&"/"&dest_id&"/"&alt_id&"/"&dtype_id&"/"&did_id&"/"&dmode_id
Source_IdA unique identifier for the Node (Switch) at this end of the connection. CGR.msc_id or CGRCC.msc_id or CGRC.cds_id or CSTSC.msc_id or CTD.msc_id or LOADM.msc_id or PRCAR.msc_id or ROU.msc_id or ROUTDM.msc_id
Source_TypeType of Source. CGR."MSC" or CGRCC."MSC" or CGRC."CDS" or CSTSC."MSC" or CTD."MSC" or LOADM."MSC" or PRCAR."MSC" or ROU."MSC" or ROUTDM."MSC"
Source_NameA user friendly name preferably unique for the Source. CGR.msc_id or CGRCC.msc_id or CGRC.cds_id or CSTSC.msc_id or CTD.msc_id or LOADM.msc_id or PRCAR.msc_id or ROU.msc_id or ROUTDM.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 or AVANHLR.hlr_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id or AVANSRR.srr_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 or AVANHLR.hlr_id&"-"&snet_id&"-"&spc_id or AVANSRR.srr_id&"-"&snet_id&"-"&spc_id
NetworkNetwork associated with the SS7 LinkSet.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVANMSC.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVANHLR.hlr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVANSRR.srr_id)
RegionRegion associated with the SS7 LinkSet.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVANMSC.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVANHLR.hlr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVANSRR.srr_id)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 LinkSet. AVANMSC.msc_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id or AVANHLR.hlr_id&"-"&snet_id&"-"&spc_id&"-"&slsn_id or AVANSRR.srr_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 or AVANHLR.hlr_id or AVANSRR.srr_id
Node_NameName of the node that this SS7 LinkSet is connected to (at this end). AVANMSC.msc_id or AVANHLR.hlr_id or AVANSRR.srr_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). AVANMSC."MSC" or AVANHLR."HLR" or AVANSRR."SRR"
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.YMTPHLR.hlr_id &"-"& sln_id or MTPMSC.msc_id &"-"& sln_id or MTPSRR.srr_id &"-"& sln_id or SLHLR.hlr_id &"-"& sln_id or SLMSC.msc_id &"-"& sln_id or SLPHLR.hlr_id &"-"& sln_id or SLPMSC.msc_id &"-"& sln_id or SLPSRR.srr_id &"-"& sln_id or SLSRR.srr_id &"-"& sln_id or SLAHLR.hlr_id &"-"& sln_id or SLAMSC.msc_id &"-"& sln_id or SLASRR.srr_id &"-"& sln_id or MTPNHLR.hlr_id &"-"& sln_id or MTPNMSC.msc_id &"-"& sln_id or SLPNHLR.hlr_id &"-"& sln_id or SLPNMSC.msc_id &"-"& sln_id or SLPNSRR.srr_id &"-"& sln_id or MTPNSRR.srr_id &"-"& sln_id
Relationship Attributes
SS7_LinkSetThe Node (MSC or HLR) that this SS7 Link is connected to (at this end).YMTPHLR.hlr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or MTPMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or MTPSRR.srr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLHLR.hlr_id&"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLPHLR.hlr_id&"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLPMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLPSRR.srr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLSRR.srr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLAHLR.hlr_id&"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLAMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLASRR.srr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or MTPNHLR.hlr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or MTPNMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or MTPNSRR.srr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLPNHLR.hlr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLPNMSC.msc_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id or SLPNSRR.srr_id &"-"& snet_id &"-"& spc_id &"-"& slsn_id
SS7_PointA unique identifier for the SS7 Point.YMTPHLR.hlr_id &"-"& snet_id &"-"& spc_id or MTPMSC.msc_id &"-"& snet_id &"-"& spc_id or MTPSRR.srr_id &"-"& snet_id &"-"& spc_id or SLHLR.hlr_id &"-"& snet_id &"-"& spc_id or SLMSC.msc_id &"-"& snet_id &"-"& spc_id or SLPHLR.hlr_id &"-"& snet_id &"-"& spc_id or SLPMSC.msc_id &"-"& snet_id &"-"& spc_id or SLPSRR.srr_id &"-"& snet_id &"-"& spc_id or SLSRR.srr_id &"-"& snet_id &"-"& spc_id or SLAHLR.hlr_id &"-"& snet_id &"-"& spc_id or SLAMSC.msc_id &"-"& snet_id &"-"& spc_id or SLASRR.srr_id &"-"& snet_id &"-"& spc_id or MTPNHLR.hlr_id &"-"& snet_id &"-"& spc_id or MTPNMSC.msc_id &"-"& snet_id &"-"& spc_id or MTPNSRR.srr_id &"-"& snet_id &"-"& spc_id or SLPNHLR.hlr_id &"-"& snet_id &"-"& spc_id or SLPNMSC.msc_id &"-"& snet_id &"-"& spc_id or SLPNSRR.srr_id &"-"& snet_id &"-"& spc_id
RegionRegion associated with the SS7 Link.Ylookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPMSC.msc_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPSRR.srr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLMSC.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPMSC.msc_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPSRR.srr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLSRR.srr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLAHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLAMSC.msc_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLASRR.srr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPNHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPNMSC.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPNHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPNMSC.msc_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPNSRR.srr_id)
NetworkNetwork associated with the SS7 Link.Ylookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPMSC.msc_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPSRR.srr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLMSC.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPMSC.msc_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPSRR.srr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLSRR.srr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLAHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLAMSC.msc_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLASRR.srr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPNHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),MTPNMSC.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPNHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPNMSC.msc_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SLPNSRR.srr_id)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 Link. MTPHLR.hlr_id &"-"& sln_id or MTPMSC.msc_id &"-"& sln_id or MTPSRR.srr_id &"-"& sln_id or SLHLR.hlr_id &"-"& sln_id or SLMSC.msc_id &"-"& sln_id or SLPHLR.hlr_id &"-"& sln_id or SLPMSC.msc_id &"-"& sln_id or SLPSRR.srr_id &"-"& sln_id or SLSRR.srr_id &"-"& sln_id or SLAHLR.hlr_id &"-"& sln_id or SLAMSC.msc_id &"-"& sln_id or SLASRR.srr_id &"-"& sln_id or MTPNHLR.hlr_id &"-"& sln_id or MTPNMSC.msc_id &"-"& sln_id or SLPNHLR.hlr_id &"-"& sln_id or SLPNMSC.msc_id &"-"& sln_id or SLPNSRR.srr_id &"-"& sln_id or MTPNSRR.srr_id &"-"& sln_id
Node_NameThe name for the network element that the SS7 Link is connected to (at this end). MTPHLR.hlr_id or MTPMSC.msc_id or MTPSRR.srr_id or SLHLR.hlr_id or SLMSC.msc_id or SLPHLR.hlr_id or SLPMSC.msc_id or SLPSRR.srr_id or SLSRR.srr_id or SLAHLR.hlr_id or SLAMSC.msc_id or SLASRR.srr_id or MTPNHLR.hlr_id or MTPNMSC.msc_id or MTPNSRR.srr_id or SLPNHLR.hlr_id or SLPNMSC.msc_id or SLPNSRR.srr_id
Node_IdThe Node (MSC or HLR) that this SS7 Link is connected to (at this end). MTPHLR.hlr_id or MTPMSC.msc_id or MTPSRR.srr_id or SLHLR.hlr_id or SLMSC.msc_id or SLPHLR.hlr_id or SLPMSC.msc_id or SLPSRR.srr_id or SLSRR.srr_id or SLAHLR.hlr_id or SLAMSC.msc_id or SLASRR.srr_id or MTPNHLR.hlr_id or MTPNMSC.msc_id or MTPNSRR.srr_id or SLPNHLR.hlr_id or SLPNMSC.msc_id or SLPNSRR.srr_id
Data_RateThe SS7 Link speed in bits per second (bit/s). MTPHLR.M210B1C2 or MTPMSC.M210B1C2 or MTPSRR.M210B1C2
Node_TypeThe type of the network element that the SS7 Link is connected to at this end. MTPHLR."HLR" or MTPMSC."MSC" or MTPSRR."SRR" or SLHLR."HLR" or SLMSC."MSC" or SLPHLR."HLR" or SLPMSC."MSC" or SLPSRR."SRR" or SLSRR."SRR" or SLAHLR."HLR" or SLAMSC."MSC" or SLASRR."SRR" or MTPNHLR."HLR" or MTPNMSC."MSC" or MTPNSRR."SRR" or SLPNHLR."HLR" or SLPNMSC."MSC" or SLPNSRR."SRR"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Adjacent_Node_IdThe Adjacent Node that this SS7 Link is connected from (at the other end). "No mapping"


Signalling_Point

Represents a signalling entity that is part of a Node.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SS7 Point.YAVAMSC.msc_id&"-"&snet_id&"-"&spc_id or SCCPMSC.msc_id&"-"&snet_id&"-"&spc_id or AVAHLR.hlr_id&"-"&snet_id&"-"&spc_id or SCCPHLR.hlr_id&"-"&snet_id&"-"&spc_id or AVASRR.srr_id&"-"&snet_id&"-"&spc_id or SCCPSRR.srr_id&"-"&snet_id&"-"&spc_id or UTRAHLR.hlr_id &"-"& snet_id &"-"& sio_id or UTRAMSC.msc_id &"-"& snet_id &"-"& sio_id or UTRASRR.srr_id &"-"& snet_id &"-"& sio_id or ACHSPC.hlr_id&"-"&snet_id&"-"&spc_id or ACVSPC.msc_id&"-"&snet_id&"-"&spc_id or MTXMSC.msc_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXHLR.hlr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXSRR.srr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_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"),AVAMSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCPMSC.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVAHLR.hlr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCPHLR.hlr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVASRR.srr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCPSRR.srr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UTRAHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UTRAMSC.msc_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UTRASRR.srr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACHSPC.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACVSPC.msc_id) or MTXMSC.REGION_ID or MTXHLR.REGION_ID or MTXSRR. REGION_ID
NetworkNetwork associated with the SS7 Point.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVAMSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCPMSC.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVAHLR.hlr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCPHLR.hlr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),AVASRR.srr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCPSRR.srr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UTRAHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UTRAMSC.msc_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),UTRASRR.srr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACHSPC.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACVSPC.msc_id) or MTXMSC.NETWORK_ID or MTXHLR.NETWORK_ID or MTXSRR.NETWORK_ID
Configuration Attributes
NameA user friendly name preferably unique for the SS7 Point. AVAMSC.msc_id&"-"&snet_id&"-"&spc_id or SCCPMSC.msc_id&"-"&snet_id&"-"&spc_id or AVAHLR.hlr_id&"-"&snet_id&"-"&spc_id or SCCPHLR.hlr_id&"-"&snet_id&"-"&spc_id or AVASRR.srr_id&"-"&snet_id&"-"&spc_id or SCCPSRR.srr_id&"-"&snet_id&"-"&spc_id or UTRAHLR.hlr_id &"-"& snet_id &"-"& sio_id or UTRAMSC.msc_id &"-"& snet_id &"-"& sio_id or UTRASRR.srr_id &"-"& snet_id &"-"& sio_id or ACHSPC.hlr_id&"-"&snet_id&"-"&spc_id or ACVSPC.msc_id&"-"&snet_id&"-"&spc_id or MTXMSC.msc_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXHLR.hlr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXSRR.srr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id
Node_IdA unique identifier for the Node. AVAMSC.msc_id or AVAHLR.hlr_id or AVASRR.srr_id or SCCPMSC.msc_id or SCCPHLR.hlr_id or SCCPSRR.srr_id or UTRAHLR.hlr_id or UTRAMSC.msc_id or UTRASRR.srr_id or ACHSPC.hlr_id or ACVSPC.msc_id or MTXMSC.msc_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXHLR.hlr&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXSRR.srr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id
Node_NameA user friendly name preferably unique for the Node. AVAMSC.msc_id or AVAHLR.hlr_id or AVASRR.srr_id or SCCPMSC.msc_id or SCCPHLR.hlr_id or SCCPSRR.srr_id or UTRAHLR.hlr_id or UTRAMSC.msc_id or UTRASRR.srr_id or ACHSPC.hlr_id or ACVSPC.msc_id or MTXMSC.msc_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXHLR.hlr&"-"& sio_id&"-"& opc_id&"-"&dspc_id or MTXSRR.srr_id&"-"& sio_id&"-"& opc_id&"-"&dspc_id
Node_TypeType of Node. AVAMSC."MSC" or SCCPMSC."MSC" or AVAHLR."HLR" or SCCPHLR."HLR" or AVASRR."SRR" or SCCPSRR."SRR" or UTRAHLR."HLR" or UTRAMSC."MSC" or ACHSPC."HLR" or ACVSPC."MSC" or MTXMSC."MSC" or MTXHLR."HLR" or MTXSRR."SRR"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Adjacent_Node_IdA unique identifier for the Adjacent Node. "No mapping"


SIP_Interface

Interface used by SIP

In the network hierarchy, the immediate parent of the SIP_Interface object is Computer_Unit.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDPrimary identifier of the SIP_Interface.YSIPPMETH.MSC_id & "/" & Unit_id & "/" & LIF_id & "/" & ATYPE_id & "/" & CTYPE_id or SIPPRESP.MSC_id & "/" & Unit_id & "/" & LIF_id & "/" & ATYPE_id & "/" & CTYPE_id
Relationship Attributes
Computer_UnitComputer unit of the SIP_Interface.YSIPPMETH.MSC_id & "/" & Unit_id or SIPPRESP.MSC_id & "/" & Unit_id
NetworkNetwork associated with the SIP_Interface.YSIPPMETH.Network_Id or SIPPRESP.Network_Id
RegionRegion associated with the SIP_Interface.YSIPPMETH.Region_Id or SIPPRESP.Region_Id
Configuration Attributes
NameMeaningful name of the SIP_Interface. SIPPMETH.MSC_id & "/" & Unit_id & "/" & LIF_id & "/" & ATYPE_id & "/" & CTYPE_id or SIPPRESP.MSC_id & "/" & Unit_id & "/" & LIF_id & "/" & ATYPE_id & "/" & CTYPE_id
Address_TypeAddress type of the SIP_Interface. SIPPMETH.ATYPE_id or SIPPRESP.ATYPE_id
Connection_TypeConnection type of the SIP_Interface. SIPPMETH.CTYPE_id or SIPPRESP.CTYPE_id
LIF_IdLIF of the SIP_Interface. SIPPMETH.LIF_id or SIPPRESP.LIF_id
Node_IdIdentifier of the Node SIPPMETH.MSC_id or SIPPRESP.MSC_id
Node_NameMeaningful name of the Node. SIPPMETH.MSC_id or SIPPRESP.MSC_id
Node_TypeType of the Node SIPPMETH."MSC" or SIPPRESP."MSC"
TechnologyTechnology of the node (e.g. UMTS, GPRS). SIPPMETH."GSM"
VersionThe hardware/software version of this Plug In Unit. "M14.1"


SMSC

Short Message Service Centres are part of the core network, used to store/forward short messages (usually up to 160 characters).

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SMSC.YSMSTY.MSC_ID&"-"&SMSCM_ID&"-"&TYPE_ID or SMS.MSC_ID&"-"&SMS.SMSCM_ID&"-ALL_TYPES" or SMSTY_AGGR.MSC_ID&"-"&SMSCM_ID&"-ALL_TYPES"
Relationship Attributes
RegionRegion associated with the SMSC.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SMSTY.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SMS.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SMSTY_AGGR.msc_id)
NetworkNetwork associated with the SMSC.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SMSTY.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SMS.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SMSTY_AGGR.msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the SMSC. SMSTY.MSC_ID&"-"&SMSCM_ID&"-"&TYPE_ID or SMS.MSC_ID&"-"&SMS.SMSCM_ID&"-ALL_TYPES" or SMSTY_AGGR.MSC_ID&"-"&SMSCM_ID&"-ALL_TYPES"
VendorManufacturer of the SMSC. "No mapping"
SMSC_VersionHardware/Software version of the SMSC. "M14.1"
SMSC_TypeType of SMSC. "MSC"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


SONET_SDH_Protection_Group

SONET SDH Protection Group

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SONET SDH Protection GroupYSONSDH.MSC_id & "/" & PGI_id
Relationship Attributes
MSCMSC associated with the SONET SDH Protection GroupYSONSDH.MSC_id
NetworkNetwork associated with the SONET SDH Protection Group.YSONSDH.Network_id
RegionRegion associated with the SONET SDH Protection Group.YSONSDH.Region_id
Configuration Attributes
NameA user friendly name for the SONET SDH Protection Group. SONSDH.MSC_id & "/" & PGI_id
TechnologyTechnology of the SONET SDH Protection Group SONSDH."GSM"
VendorManufacturer of the SONET SDH Protection Group SONSDH."Nokia"
VersionSoftware Version of the SONET SDH Protection Group "M14.1"


SRR

The Service Routing Register is a network element which provides Mobile Number Portability for mobile subscribers. It provides the following functionality: Signalling Relay Function for NP support and Mobile Application Part Application Termination Function.

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the service routing registerYREJSRR.srr_id or SRRM.srr_id or LOCSRR.srr_id or SCCPSRR.srr_id or AVASRR.srr_id or SCCSRR.srr_id or STASRR.srr_id or SIGSSRR.srr_id or SIGSRR.srr_id or MTXSRR.srr_id
Relationship Attributes
RegionRegion associated with the SRRYREJSRR.region_id or SRRM.region_id or LOCSRR.region_id or SCCPSRR.region_id or AVASRR.region_id or SCCSRR.region_id or STASRR.region_id or SIGSSRR.region_id or SIGSRR.region_id or MTXSRR.region_id
NetworkIdentifier of the NetworkYREJSRR.network_id or SRRM.network_id or LOCSRR.network_id or SCCPSRR.network_id or AVASRR.network_id or SCCSRR.network_id or STASRR.network_id or SIGSSRR.network_id or SIGSRR.network_id or MTXSRR.network_id
Configuration Attributes
NameA user-friendly name for the service routing register REJSRR.srr_id or SRRM.srr_id or LOCSRR.srr_id or SCCPSRR.srr_id or AVASRR.srr_id or SCCSRR.srr_id or STASRR.srr_id or SIGSSRR.srr_id or SIGSRR.srr_id or MTXSRR.srr_id
TechnologyGSM, GPRS, UMTS, etc. "GSM"
VendorManufacturer of the SRR "Nokia"


STM1_Set

STM1 set

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the STM1 SetYSTM1.MSC_id & "/" & SET_id
Relationship Attributes
MSCMSC associated with the STM1 SetYSTM1.MSC_id
NetworkNetwork associated with the STM1 Set.YSTM1.Network_id
RegionRegion associated with the STM1 Set.YSTM1.Region_id
Configuration Attributes
NameA user friendly name for the STM1 Set. STM1.MSC_id & "/" & SET_id
TechnologyTechnology of the STM1 Set STM1."GSM"
VendorManufacturer of the STM1 Set STM1."Nokia"
VersionSoftware Version of the STM1 Set "M14.1"


Timeslot

Timeslot

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDTimeslot identifierYCRCDS.cds_id& "-" &pcm_id& "-" & tsl_id or CRTSL.msc_id& "-" &pcm_id& "-" & tsl_id
Relationship Attributes
RegionRegion identifierY lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CRTSL.msc_id) or lookup("nc_cds","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CRCDS.cds_id)
NetworkNetwork identifierYlookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CRTSL.msc_id) or lookup("nc_cds","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),CRCDS.cds_id)
Configuration Attributes
NameTimeslot nameYCRCDS.cds_id& "-" &pcm_id& "-" & tsl_id or CRTSL.msc_id& "-" &pcm_id& "-" & tsl_id
VendorVendor name "Nokia"
VersionVesion name "M14.1"
TechnologyTechnology name "GSM"


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 or ACVDEST.msc_id or ACVMSC.msc_id or DESVLR.msc_id or PLMNV.msc_id or VLRMSC.msc_id or VLRNMSC.msc_id
Relationship Attributes
MSCThe MSC to which the VLR belongs.YVLR1MSC.msc_id or ACVDEST.msc_id or ACVMSC.msc_id or DESVLR.msc_id or PLMNV.msc_id or VLRMSC.msc_id or VLRNMSC.msc_id
NetworkNetwork associated with the VLR.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),VLR1MSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACVDEST.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACVMSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), DESVLR.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), PLMNV.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), VLRMSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), VLRNMSC.msc_id)
RegionRegion associated with the VLR.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),VLR1MSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACVDEST.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), ACVMSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), DESVLR.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), PLMNV.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), VLRMSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"), VLRNMSC.msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the VLR. VLR1MSC.msc_id or ACVDEST.msc_id or ACVMSC.msc_id or DESVLR.msc_id or PLMNV.msc_id or VLRMSC.msc_id or VLRNMSC.msc_id
VLR_VersionHardware/Software version of the VLR. "M14.1"
VendorManufacturer of the VLR. "Nokia"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


VMGW

Virtual MGW

In the network hierarchy, the immediate parent of the VMGW object is MGW.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Virtual MGWYMGWTCV.MSC_id & "/" & PMGW_id & "/" & VMGW_id
Relationship Attributes
MGWMGW associated with the Virtual MGWYMGWTCV.PMGW_id
NetworkNetwork associated with the Virtual MGW.YMGWTCV.Network_id
RegionRegion associated with the Virtual MGW.YMGWTCV.Region_id
Configuration Attributes
NameA user friendly name for the Virtual MGW. MGWTCV.MSC_id & "/" & PMGW_id & "/" & VMGW_id
TechnologyTechnology of the Virtual MGW MGWTCV."GSM"
VendorManufacturer of the Virtual MGW MGWTCV."Nokia"
VersionSoftware Version of the Virtual MGW "M14.1"


VMSC

VMSC

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the VMSC.YVMSCT.msc_id & "/" & vmsc_id
Relationship Attributes
MSCThe MSC to which the VMSC belongs.YVMSCT.msc_id
NetworkNetwork associated with the VMSC.Ylookup("nc_msc","network_id",utime(VMSCT.StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
RegionRegion associated with the VMSC.Ylookup("nc_msc","region_id",utime(VMSCT.StartDate & " " & StartTime,"%Y-%m-%d %R"),msc_id)
Configuration Attributes
NameA user friendly name preferably unique for the VMSC. VMSCT.msc_id & "/" & vmsc_id
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
VMSC_VersionHardware/Software version of the VMSC. "M14.1"
VendorManufacturer of the VMSC. "Nokia"


5.2 Reference Objects

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

AIUR

The air interface user rates

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the AIUR (Air interface User Rate)YGBSAIUR.aiur_id or UMTSAI.umtsaiur_id
Configuration Attributes
NameA user-friendly name for the AIUR GBSAIUR.aiur_id or UMTSAI.umtsaiur_id


Announcement_Device

An announcement device

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the announcement deviceYANN.msc_id&"-"&ann_id
Relationship Attributes
MSCThe associated MSCYANN.msc_id
Configuration Attributes
NameA user-friendly name for the announcement device ANN.msc_id&"-"&ann_id


Basic_Service

A basic service code

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the basic serviceYH1BS.hlr_id&"-"&bservice_id
Relationship Attributes
MSCA unique identifier for the MSC.YH1BS.hlr_id
Configuration Attributes
NameA user-friendly name for the basic service H1BS.hlr_id&"-"&bservice_id


Call_Type

Call type means the combination of the information transfer capability (ITC) used, data service unit used, and the number of traffic channels allocated.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the call typeYDSE.CALLTYPE_ID or IWFCT.CALLTYPE_ID or IWC.CALLTYPE_ID
Configuration Attributes
NameA user-friendly name for the call type DSE.CALLTYPE_ID or IWFCT.CALLTYPE_ID or IWC.CALLTYPE_ID


CDR_Type

Call data record type

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDCDR Type identifierYCDRT.cdrtype_id
Configuration Attributes
NameCDR Type name CDRT.cdrtype_id
TechnologyTechnology "GSM"
VersionVersion "M14.1"


Circuit_Group_Set

A circuit group set

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the circuit group setYCGRCC.cgr_id
Configuration Attributes
NameA user-friendly name for the circuit group set CGRCC.cgr_id
Circuit_Group10_NumberThe circuit group number CGRCC.M136B2C15
Circuit_Group1_NumberThe circuit group number CGRCC.M136B2C6
Circuit_Group2_NumberThe circuit group number CGRCC.M136B2C7
Circuit_Group3_NumberThe circuit group number CGRCC.M136B2C8
Circuit_Group4_NumberThe circuit group number CGRCC.M136B2C9
Circuit_Group5_NumberThe circuit group number CGRCC.M136B2C10
Circuit_Group6_NumberThe circuit group number CGRCC.M136B2C11
Circuit_Group7_NumberThe circuit group number CGRCC.M136B2C12
Circuit_Group8_NumberThe circuit group number CGRCC.M136B2C13
Circuit_Group9_NumberThe circuit group number CGRCC.M136B2C14


Codec

The codec values for an object.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the codec.YMGWCU.codec_id
Configuration Attributes
NameA user friendly name for the codec MGWCU.codec_id


Control_Unit

A control unit.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the control unitYCNTL.unit_id or CNTLC.unit_id or CNTLLM.unit_id
Configuration Attributes
NameA user-friendly name for the control unit CNTL.unit_id or CNTLC.unit_id or CNTLLM.unit_id


Destination_Point

The destination point code in the network

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

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the destination pointYMTXMSC.msc_id&"-"&dspc_id or MTXHLR.hlr_id&"-"&dspc_id or MTXSRR.srr_id&"-"&dspc_id
Relationship Attributes
RegionIdentifier of the RegionYMTXMSC.REGION_ID or MTXHLR.REGION_ID or MTXSRR. REGION_ID
NetworkIdentifier of the NetworkYMTXMSC.NETWORK_ID or MTXHLR.NETWORK_ID or MTXSRR.NETWORK_ID
NodeThe unique identifier of the node id.YMTXMSC.msc_id or MTXHLR.hlr_id or MTXSRR.srr_id
Configuration Attributes
NameA user-friendly name for the destination point MTXMSC.msc_id&"-"&dspc_id or MTXHLR.hlr_id&"-"&dspc_id or MTXSRR.srr_id&"-"&dspc_id
Node_TypeType of node. MTXMSC."MSC" or MTXHLR."HLR" or MTXSRR."SRR"
Node_NameMeaningful name for the Node MTXMSC.msc_id or MTXHLR.hlr_id or MTXSRR.srr_id
VendorManufacturer of the Node "Nokia"
VersionThe hardware/software version of the Node that is representing this Destination Point. "M14.1"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


Destination_Type

Destination type

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDDestination type identifierYNUPD.desttype_id &"-"& dest_id
Configuration Attributes
NameDestination type name NUPD.desttype_id &"-"& dest_id


DNI

Direction Network Index.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDDirection Network Index identifierYSRRM.dni_id
Configuration Attributes
NameDirection network name SRRM.dniname_id
DirectionDirection, can be incoming or outgoing SRRM.dire_id


FNUR

Fixed network user rates

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the FNUR (fixed network user rate)YGBSFNUR.fnur_id or UMTSFN.umtsfnur_id
Configuration Attributes
NameA user-friendly name for the FNUR (fixed network user rate) GBSFNUR.fnur_id or UMTSFN.umtsfnur_id


IN_Service

An Intelligent Network Service

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the IN serviceYINS.INSERVICE_id or CAPMD.INSERVICE_id or CAPMS.INSERVICE_id or IDPHD.INSERVICE_id or IDPHS.INSERVICE_id or IDPMD.INSERVICE_id or IDPMS.INSERVICE_id
Configuration Attributes
NameA user-friendly name for the IN service INS.INSERVICE_id or CAPMD.INSERVICE_id or CAPMS.INSERVICE_id or IDPHD.INSERVICE_id or IDPHS.INSERVICE_id or IDPMD.INSERVICE_id or IDPMS.INSERVICE_id


Incoming_Number_Destination

The incoming number destination

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the destinationYDTD.indesttype_id&"-"&indest_id
Configuration Attributes
NameA user-friendly name for the destination DTD.indesttype_id&"-"&indest_id
Incoming_Number_Destination_TypeThe type of the destination if DTD.indesttype_id=10 then "NAT" else if DTD.indesttype_id=11 then "INT" else if DTD.indesttype_id=12 then "SUB" else "UNKNOWN"


MGW_Event

The different events detected on the interface between the MSC Server and Multimedia Gateway

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the MGW eventYEVEM.EVENT_ID
Configuration Attributes
NameA user-friendly name for the MGW event EVEM.EVENT_ID


MSC_Circuit

The termid in the MSC.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the MSC circuitYCRTERM.term_id
Configuration Attributes
NameA user-friendly name for the MSC circuit CRTERM.term_id
PCM_Of_CircuitThe PCM of the circuit  
TSL_Of_CircuitThe TSL of the circuit  


MSC_Clear_Code

The clear codes for an MSC

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the MSC clear codeYCCDES.CC_ID or CCMEA.CC_ID or CC2.CC_ID or DATA.CC_ID or RNCMCC.CC_ID or SPCCC.CC_ID or FQDNCC.CC_ID or CC1.CC_ID or CGRCC.CC_ID
Configuration Attributes
NameA user-friendly name for the MSC clear code CCDES.CC_ID or CCMEA.CC_ID or CC2.CC_ID or DATA.CC_ID or RNCMCC.CC_ID or SPCCC.CC_ID or FQDNCC.CC_ID or CC1.CC_ID or CGRCC.CC_ID


Number_Destination

Number destination (MSISDN/ISDN) (max.16 digits)

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the number destinationYDESTCG.DEST_ID or NUMD.DEST_ID &"-" &DESTTYPE_ID&"-"&DESTDIR_ID or CCDES.DEST_ID or DCALL.DEST_ID or IND.DEST_ID or CTD.DEST_ID&"-"&DESTTYPE_ID or DESVLR.DEST_ID or ACVDEST.DEST_ID
Configuration Attributes
NameA user-friendly name for the number destination DESTCG.DEST_ID or NUMD.DEST_ID&"-"&DESTTYPE_ID or CCDES.DEST_ID or DCALL.DEST_ID or IND.DEST_ID or CTD.DEST_ID&"-"&DESTTYPE_ID or DESVLR.DEST_ID or ACVDEST.DEST_ID
Number_Destination_TypeThe type of the number destination NUMD.DESTTYPE_ID or CTD.DESTTYPE_ID
Number_destination_directionNumber destination direction identifier. NUMD.destdir_id


Originating_Point

The origination point code

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the originating pointYMTXMSC.opc_id or MTXHLR.opc_id or MTXSRR.opc_id
Configuration Attributes
NameA user-friendly name for the originating point MTXMSC.opc_id or MTXHLR.opc_id or MTXSRR.opc_id


Outgoing_Number_Destination

The outgoing number destination

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the destinationYDTD.outdesttype_id&"-"&outdest_id
Configuration Attributes
NameA user-friendly name for the destination DTD.outdesttype_id&"-"&outdest_id
Outgoing_Number_Destination_TypeThe type of the destination. (NAT, INT, SUB) if outdesttype_id=10 then "NAT" else if outdesttype_id=11 then "INT" else if outdesttype_id=12 then "SUB" else "UNKNOWN"


Reject_Cause

Reject cause

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Reject_Cause.YSSAPHSRC.RC_Id or CAPMDRC.RC_Id or IOC2HDRC.RC_Id or IOCOHDRC.RC_Id or MAPHDTRC.RC_Id & "/" & VER_Id or SSAPMSRC.RC_Id or MAPMNIRC.RC_Id & "/" & VER_Id or MAPMSNRC.RC_Id & "/" & VER_Id or MAPHNIRC.RC_Id & "/" & VER_Id or MAPHSNRC.RC_Id & "/" & VER_Id or CAPMSRC.RC_Id or IOC2MDRC.RC_Id or IOC2MSRC.RC_Id or IOCOMDRC.RC_Id or IOCOMSRC.RC_Id
Configuration Attributes
NameA user friendly name for the Reject_Cause. SSAPHSRC.RC_Id or CAPMDRC.RC_Id or IOC2HDRC.RC_Id or IOCOHDRC.RC_Id or MAPHDTRC.RC_Id & "/" & VER_Id or SSAPMSRC.RC_Id or MAPMNIRC.RC_Id & "/" & VER_Id or MAPMSNRC.RC_Id & "/" & VER_Id or MAPHNIRC.RC_Id & "/" & VER_Id or MAPHSNRC.RC_Id & "/" & VER_Id or CAPMSRC.RC_Id or IOC2MDRC.RC_Id or IOC2MSRC.RC_Id or IOCOMDRC.RC_Id or IOCOMSRC.RC_Id
TechnologyTechnology of the Reject_Cause SSAPHSRC."GSM"
VendorManufacturer of the Reject_Cause SSAPHSRC."Nokia"
VersionSoftware Version of the Reject_Cause "M14.1"


Security_Counter

A security event

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the security counterYRSEC.secevnt_id or SSEC.secevnt_id or LSEC.secevnt_id
Configuration Attributes
NameA user-friendly name for the security counter RSEC.secevnt_id or SSEC.secevnt_id or LSEC.secevnt_id


SGSN_address

The ISDN address of a SGSN.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDSGSN ISDN address IdentifierYVLRMS.dest_id
Configuration Attributes
NameSGSN ISDN address name VLRMS.dest_id


Signal_Protocol

The signalling protocol

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the signal protocolYCC2.protocol_id or REH.ticketserv_id or REM.ticketserv_id or RES.ticketserv_id or RNCMCC.protocol_id or SPCCC.protocol_id or CC1.protocol_id or CGRCC.protocol_id
Configuration Attributes
NameA user-friendly name for the signal protocol CC2.protocol_id or REH.ticketserv_id or REM.ticketserv_id or RES.ticketserv_id or RNCMCC.protocol_id or SPCCC.protocol_id or CGRCC.protocol_id


Signalling_Network

The signalling network

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the signalling networkYLOCHLR.snet_id or SUBMSC.snet_id or LOCMSC.snet_id or TTRAMSC.snet_id or SUBHLR.snet_id or TTRAHLR.snet_id or SCCPMSC.snet_id or SCCPHLR.snet_id or SCCPSRR.snet_id or STAHLR.snet_id or LOCSRR.snet_id or SUBSRR.snet_id or TTRASRR.snet_id or UTRAHLR.snet_id or UTRAMSC.snet_id or UTRASRR.snet_id
Configuration Attributes
NameA user-friendly name for the signalling network LOCHLR.snet_id or SUBMSC.snet_id or LOCMSC.snet_id or TTRAMSC.snet_id or SUBHLR.snet_id or TTRAHLR.snet_id or SCCPMSC.snet_id or SCCPHLR.snet_id or SCCPSRR.snet_id or STAHLR.snet_id or LOCSRR.snet_id or SUBSRR.snet_id or TTRASRR.snet_id or UTRAHLR.snet_id or UTRAMSC.snet_id or UTRASRR.snet_id


Signalling_Transfer_Point

A signalling transfer point

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the signalling transfer pointYSIGSMSC.msc_id&"-"&spc_id&"-"&stp_id or SIGSHLR.hlr_id&"-"&spc_id&"-"&stp_id or SIGSSRR.srr_id&"-"&spc_id&"-"&stp_id
Relationship Attributes
SS7_PointThe related signalling pointYSIGSMSC.msc_id&"-"&snet_id&"-"&spc_id or SIGSHLR.hlr_id&"-"&snet_id&"-"&spc_id or SIGSSRR.srr_id&"-"&snet_id&"-"&spc_id
Configuration Attributes
NameA user-friendly name for the signalling transfer point SIGSMSC.msc_id&"-"&spc_id&"-"&stp_id or SIGSHLR.hlr_id&"-"&spc_id&"-"&stp_id or SIGSSRR.srr_id&"-"&spc_id&"-"&stp_id


SIO

The service information octect

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the SIOYMTXMSC.sio_id or UTRAMSC.sio_id or UTRAHLR.sio_id or MTXHLR.sio_id or UTRASRR.sio_id or MTXSRR.sio_id
Configuration Attributes
NameA user-friendly name for the SIO MTXMSC.sio_id or UTRAMSC.sio_id or UTRAHLR.sio_id or MTXHLR.sio_id or UTRASRR.sio_id or MTXSRR.sio_id


SIP_Method

The Methods used by SIP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe identifier used for SIP MethodYSIPPMETH.METH_Id
Configuration Attributes
NameName for the SIP Method SIPPMETH.METH_Id
TechnologyTechnology for the SIP Method "GSM"
VendorVendor of the SIP Method "Nokia"
VersionVersion of the SIP Method "M14.1"


SIP_Response

The Responses used by SIP.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDIdentifier for the SIP ResponseYSIPPRESP.METH_Id & "/" & RESP_Id
Configuration Attributes
NameName for the SIP Response SIPPRESP.METH_Id & "/" & RESP_Id
TechnologyTechnology for the SIP ResponseY"GSM"
VendorVendor of the SIP Response "Nokia"
VersionVersion of the SIP Response "M14.1"


SRR_Service

The SRR service operation codes

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the SRR serviceYSRRSSP.dni_id
Configuration Attributes
NameA user-friendly name for the SRR service SRRSSP.dniname_id


Subscriber_Facility

The facility abbreviation

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the subscriber facilityYSERVI.msc_id&"-"&service_id
Relationship Attributes
MSCThe associated MSCYSERVI.msc_id
Configuration Attributes
NameA user-friendly name for the subscriber facility SERVI.msc_id&"-"&service_id


Subsystem

The subsystem in the signaling network

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the subsystemYSUBMSC.msc_id&"-"&ssn_id or TTRAMSC.msc_id&"-"&ssn_id or SUBHLR.hlr_id&"-"&ssn_id or TTRAHLR.hlr_id&"-"&ssn_id or SCCMSC.msc_id&"-"&ssn_id or SCCHLR.hlr_id&"-"&ssn_id or SCCSRR.srr_id&"-"&ssn_id or TTRASRR.srr_id&"-"&ssn_id or SUBSRR.srr_id&"-"&ssn_id
Relationship Attributes
RegionRegion associated with the Region.Ylookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SUBMSC.msc_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TTRAMSC.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SUBHLR.hlr_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TTRAHLR.hlr_id) or lookup("nc_msc","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCMSC.msc_id) or lookup("nc_hlr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCHLR.hlr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCSRR.srr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TTRASRR.srr_id) or lookup("nc_srr","region_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SUBSRR.srr_id)
NetworkNetwork associated with the subsystem.Ylookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SUBMSC.msc_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TTRAMSC.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SUBHLR.hlr_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TTRAHLR.hlr_id) or lookup("nc_msc","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCMSC.msc_id) or lookup("nc_hlr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCHLR.hlr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SCCSRR.srr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),TTRASRR.srr_id) or lookup("nc_srr","network_id",utime(StartDate & " " & StartTime,"%Y-%m-%d %R"),SUBSRR.srr_id)
Configuration Attributes
NameA user-friendly name for the subsystem SUBMSC.msc_id&"-"&ssn_id or TTRAMSC.msc_id&"-"&ssn_id or SUBHLR.hlr_id&"-"&ssn_id or TTRAHLR.hlr_id&"-"&ssn_id or SCCMSC.msc_id&"-"&ssn_id or SCCHLR.hlr_id&"-"&ssn_id or SCCSRR.srr_id&"-"&ssn_id or TTRASRR.srr_id&"-"&ssn_id or SUBSRR.srr_id&"-"&ssn_id
Node_IdThe unique identifier of the node id. SUBMSC.msc_id or TTRAMSC.msc_id or SUBHLR.hlr_id or TTRAHLR.hlr_id or TTRASRR.srr_id or SUBSRR.srr_id
Node_NameNode Name. SUBMSC.msc_id or TTRAMSC.msc_id or SUBHLR.hlr_id or TTRAHLR.hlr_id or TTRASRR.srr_id or SUBSRR.srr_id
Node_TypeType of the node identifier (MSC, HLR, etc.) SUBMSC."MSC" or TTRAMSC."MSC" or SUBHLR."HLR" or TTRAHLR."HLR" or SCCMSC."MSC" or SCCHLR."HLR" or SCCSRR."SRR" or TTRASRR."SRR" or SUBSRR."SRR"
VendorManufacturer of the equipment/element that is supporting this subsystem. "Nokia"
VersionHardware/Software version of the equipment/element that is supporting this subsystem. "M14.1"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


Supplementary_Service

Supplementary Services supported by voice switches.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Supplementary Service.YSSERV.sservice_id
Configuration Attributes
NameA user friendly name preferably unique for the Supplementary Service. SSERV.sservice_id


TCPIP_Stack

TCP/IP stack within a unit.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDTCP/IP stack identifier.YTCPIP.unit_id
Configuration Attributes
NameTCP/IP stack name TCPIP.unit_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 or MGWTCP.TCAT_ID or MGWTCV.TCAT_ID
Configuration Attributes
NameA user friendly name preferably unique for the Traffic Type. TC.TCAT_ID or MGWTCP.TCAT_ID or MGWTCV.TCAT_ID
DirectionDirection of Traffic.  
IS_SwitchedIs the traffic switched? "No mapping"


Transdir

Transdir

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Transdir.YMLANEMBT.TRA_Id
Configuration Attributes
NameA user friendly name for the Transdir. MLANEMBT.TRA_Id
TechnologyTechnology of the Transdir MLANEMBT."GSM"
VendorManufacturer of the Transdir MLANEMBT."Nokia"
VersionSoftware Version of the Transdir "M14.1"


UPD

User Plane Destination

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the UPDYUPD.upd_id or NUPD.upd_id or CSTSU.upd_id
Configuration Attributes
NameA user-friendly name for the UPD UPD.upd_id or NUPD.upd_id or CSTSU.upd_id


VLR_Address

The ISDN address of a VLR

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDThe unique identifier of the VLR addressYACHDEST.dest_id or VLRME.dest_id
Configuration Attributes
NameA user-friendly name for the VLR address ACHDEST.dest_id or VLRME.dest_id


6. Busy Hours

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

ObjectBusy HourAcronymDefining KPI
CDSNokia_CDS_Traffic_Busy_HournkcdstbhCDS.Nokia.GSM.Control_Unit.cntl_erlangs
D_LinkNokia_D_Link_Total_Traffic_Busy_HournkdlttbhD_Link.Nokia.GSM.Traffic.total_octets
HLRNokia_HLR_Subscribers_Busy_HournkhlrsubbhHLR.Nokia.GSM.Mobility.tot_succ_home_lu
Interface_LANNokia_Interface_LAN_Packet_Traffic_Busy_HournklanpkbhInterface_LAN.Nokia.GSM.LAN_Unit_Utilisation.TOTAL_TX_AND_RX_PACKETS
Interface_MAPNokia_IMAP_Operations_Incoming_Outgoing_Busy_HournkimapopbhInterface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_TOTAL_I_O_STARTED_OCS
MGWNokia_MGW_Incoming_Request_Busy_HournkmgwhmbhMGW.Nokia.GSM.Megaco.totalnumberofhandledmessages
MSCNokia_MSC_Traffic_Busy_HournkmtbhMSC.Nokia.GSM.Traffic_Category_All_Types.tcat_traff
MSCNokia_MSC_Traffic_Type_Busy_HournkmttbhMSC.Nokia.GSM.Traffic_Category.tcat_traff
ProcessorNokia_Processor_CDS_Load_Busy_HournkpclbhProcessor.Nokia.GSM.CDS_CPU_Load.comp_average_load
ProcessorNokia_Processor_HLR_Load_Busy_HournkphlbhProcessor.Nokia.GSM.HLR_CPU_Load.load
ProcessorNokia_Processor_SRR_Load_Busy_HournkpslbhProcessor.Nokia.GSM.SRR_CPU_Load.compl_load_percent_x10
ProcessorNokia_Processor_MSC_Load_Busy_HournkpmlbhProcessor.Nokia.GSM.MSC_CPU_Load.load
Route_IFNokia_Route_IF_Bothway_MSC_Busy_HournkrbmbhRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_accepted_bothway
Route_IFNokia_Route_IF_Incoming_CDS_Busy_HournkricbhRoute_IF.Nokia.GSM.CDS_Circuit_Group.cgrcgroup_erlangs_in_x_100
Route_IFNokia_Route_IF_Outgoing_MSC_Busy_HournkrombhRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_accepted_out
Route_IFNokia_Route_IF_Outgoing_CDS_Busy_HournkrocbhRoute_IF.Nokia.GSM.CDS_Circuit_Group.cgrcgroup_erlangs_out_x_100
Route_IFNokia_Route_IF_Incoming_MSC_Busy_HournkrimbhRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_accepted_in
Signalling_LinkNokia_SS7_HLR_Incoming_Utilisation2_Busy_HournkslhlrxbhSignalling_Link.Nokia.GSM.HLR_Signalling_Point_Util_2.incoming_utilisation
Signalling_LinkNokia_SS7_HLR_Incoming_Utilisation_Busy_HournkslhrxbhSignalling_Link.Nokia.GSM.HLR_Signalling_Link_Utilisation.incoming_utilisation
Signalling_LinkNokia_SS7_SRR_Outgoing_Utilisation_Busy_HournkslstxbhSignalling_Link.Nokia.GSM.SRR_Signalling_Link_Utilisation.outgoing_utilisation
Signalling_LinkNokia_SS7_SRR_Outgoing_Utilisation2_Busy_HournkslsrtxbhSignalling_Link.Nokia.GSM.SRR_Signalling_Point_Util_2.outgoing_utilisation
Signalling_LinkNokia_SS7_SRR_Incoming_Utilisation_Busy_HournkslsrxbhSignalling_Link.Nokia.GSM.SRR_Signalling_Link_Utilisation.incoming_utilisation
Signalling_LinkNokia_SS7_SRR_Incoming_Utilisation2_Busy_HournkslsrrxbhSignalling_Link.Nokia.GSM.SRR_Signalling_Point_Util_2.incoming_utilisation
Signalling_LinkNokia_SS7_Outgoing_Utilisation_Busy_HournksltxbhSignalling_Link.Nokia.GSM.MSC_Signalling_Link_Utilisation.outgoing_utilisation
Signalling_LinkNokia_SS7_MSC_Outgoing_Utilisation2_Busy_HournkslmtxbhSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2.outgoing_utilisation
Signalling_LinkNokia_SS7_MSC_Incoming_Utilisation2_Busy_HournkslmrxbhSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2.incoming_utilisation
Signalling_LinkNokia_SS7_Incoming_Utilisation_Busy_HournkslrxbhSignalling_Link.Nokia.GSM.MSC_Signalling_Link_Utilisation.incoming_utilisation
Signalling_LinkNokia_SS7_HLR_Outgoing_Utilisation_Busy_HournkslhtxbhSignalling_Link.Nokia.GSM.HLR_Signalling_Link_Utilisation.outgoing_utilisation
Signalling_LinkNokia_SS7_HLR_Outgoing_Utilisation2_Busy_HournkslhltxbhSignalling_Link.Nokia.GSM.HLR_Signalling_Point_Util_2.outgoing_utilisation
SIP_InterfaceNokia_SIP_Requests_Busy_HournksipreqbhSIP_Interface.Nokia.GSM.SIP_Requests.SIP_PROT_TOT_NUM_REQS
SMSCNokia_SMSC_Total_SMS_Busy_HournksmstbhSMSC.Nokia.GSM.SMS_Measurements.all_sms
SRRNokia_SRR_Open_Transaction_Busy_HournksrrotbhSRR.Nokia.GSM.TCAP_Transaction.open
VLRNokia_VLR_Subscribers_Busy_HournkvsubbhVLR.Nokia.GSM.Subscribers.tot_curr_subsc


7. Constants


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

None.

8. Performance Indicators

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

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


ASSOIND Performance Indicators

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


ASSOIND.Nokia.GSM.Association_Index

Association Index measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
m3ua_cumul_unavailable_timeACCUMULATIONINT8The cumulative duration of the unavailability of the association index in seconds for the whole measurement time from the beginning to current time.M3UAMI.M661B3C1 or M3UAHI.M661B3C1 or M3UASI.M661B3C1 
m3ua_messages_receivedACCUMULATIONINT8The number of received messages on the association.M3UAMI.M661B3C3 or M3UAHI.M661B3C3 or M3UASI.M661B3C3 
m3ua_messages_sentACCUMULATIONINT8The number of sent messages on the M3UA association.M3UAMI.M661B3C4 or M3UAHI.M661B3C4 or M3UASI.M661B3C4 
m3ua_octets_receivedACCUMULATIONINT8The number of octets received on the M3UA association.M3UAMI.M661B3C5 or M3UAHI.M661B3C5 or M3UASI.M661B3C5 
m3ua_octets_sentACCUMULATIONINT8The number of octets sent on the M3UA association.M3UAMI.M661B3C6 or M3UAHI.M661B3C6 or M3UASI.M661B3C6 
m3ua_sctp_duplicated_tsnACCUMULATIONINT8The number of duplicated TSN received on SCTP per M3UA association.M3UAMI.M661B4C6 or M3UAHI.M661B4C6 or M3UASI.M661B4C6 
m3ua_sctp_octets_receivedACCUMULATIONINT8The number of octets received on SCTP per M3UA association.M3UAMI.M661B4C3 or M3UAHI.M661B4C3 or M3UASI.M661B4C3 
m3ua_sctp_octets_sentACCUMULATIONINT8The number of octets sent on SCTP per M3UA association.M3UAMI.M661B4C4 or M3UAHI.M661B4C4 or M3UASI.M661B4C4 
m3ua_sctp_packets_receivedACCUMULATIONINT8The number of packets received on SCTP per M3UA association.M3UAMI.M661B4C1 or M3UAHI.M661B4C1 or M3UASI.M661B4C1 
m3ua_sctp_packets_retransmitACCUMULATIONINT8The number of packets retransmitted on SCTP per M3UA association.M3UAMI.M661B4C5 or M3UAHI.M661B4C5 or M3UASI.M661B4C5 
m3ua_sctp_packets_sentACCUMULATIONINT8The number of packets sent on SCTP per M3UA association.M3UAMI.M661B4C2 or M3UAHI.M661B4C2 or M3UASI.M661B4C2 
m3ua_unavailableACCUMULATIONINT8The number of times the association index is unavailable.M3UAMI.M661B3C2 or M3UAHI.M661B3C2 or M3UASI.M661B3C2 


ASSOSET Performance Indicators

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


ASSOSET.Nokia.GSM.Association_Set

Association Set measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
m3ua_asso_set_unavailable_timeACCUMULATIONINT8The cumulative duration of the unavailability of the association set in seconds for the whole measurement time from the beginning to current time.M3UAMS.M661B2C1 or M3UAHS.M661B2C1 or M3UASS.M661B2C1 
m3ua_asso_set_unavailableACCUMULATIONINT8The number of times the association set is unavailable.M3UAMS.M661B2C2 or M3UAHS.M661B2C2 or M3UASS.M661B2C2 


BSC Performance Indicators

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


BSC.Nokia.GSM.Call_setup_service

Call setup service data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cssmt_bsc_failed_bidsACCUMULATIONINT8Number of unsuccessful call setup service attempts in the BSC level.CSSB.M387B3C4 
cssmt_bsc_failed_mean_timeACCUMULATIONINT8Mean time of unsuccessful call setup service attempts in seconds in ASCII reports and in 10 ms in XML reports. Mean time is calculated by dividing the value of the unsuccessful total call setup service time reservation by the value of unsuccessful call setup service attempts.CSSB.M387B3C5 
cssmt_bsc_succ_bidsACCUMULATIONINT8Number of successful call setup service attempts in the BSC level.CSSB.M387B3C2 
cssmt_bsc_succ_mean_timeACCUMULATIONINT8Mean time of successful call setup service attempts in seconds in ASCII reports and in 10 ms in XML reports. Mean time is calculated by dividing the value of the successful total call setup service time reservation by the value of successful call setup service attempts.CSSB.M387B3C3 


BSC.Nokia.GSM.Handover

The handover measurement shows the number of different type of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
from_other_msc_to_bsc_nokACCUMULATIONINT8Unsuccessful handovers to the BSC from another MSCHOBSCM.M338B3C12 
from_other_msc_to_bsc_okACCUMULATIONINT8Successful handovers to the BSC from another MSCHOBSCM.M338B3C11 
from_other_msc_to_rnc_nokACCUMULATIONINT8Unsuccessful handovers to the RNC from another MSCHORNCM.M338B3C12 
from_other_msc_to_rnc_okACCUMULATIONINT8Successful handovers to the RNC from another MSCHORNCM.M338B3C11 
neighbour_bsc_from_nokACCUMULATIONINT8Unsuccessful handovers from BSCs in other MSCHOBSCM.M338B3C8 
neighbour_bsc_from_okACCUMULATIONINT8Successful handovers from BSCs in other MSCHOBSCM.M338B3C7 
neighbour_bsc_to_nokACCUMULATIONINT8Unsuccessful handovers to BSCs in other MSCHOBSCM.M338B3C6 
neighbour_bsc_to_okACCUMULATIONINT8Successful handovers to BSCs in other MSCHOBSCM.M338B3C5 
neighbour_rnc_from_nokACCUMULATIONINT8Unsuccessful handovers from RNCs in other MSCHORNCM.M338B3C8 
neighbour_rnc_from_okACCUMULATIONINT8Successful handovers from RNCs in other MSCHORNCM.M338B3C7 
neighbour_rnc_to_nokACCUMULATIONINT8Unsuccessful handovers to RNCs in other MSCHORNCM.M338B3C6 
neighbour_rnc_to_okACCUMULATIONINT8Successful handovers to RNCs in other MSCHORNCM.M338B3C5 


CAP_Error_Code Performance Indicators

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


CAP_Error_Code.Nokia.GSM.CAP_Operation_Error

CAP operation Errors

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_OC_EC_NUMBERACCUMULATIONINT8The number of CAP operations terminated due to error during the measurement period.CAPMDEC.M200B9C1 or CAPMSEC.M200B9C1nkmtbh


CAP_Op_Code Performance Indicators

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


CAP_Op_Code.Nokia.GSM.CAP_Operation

CAP Operations

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_OC_ABORTEDACCUMULATIONINT8Shows the number of aborted CAP operations due to internal errors, or TCAP user, or provider aborts during the measurement period.CAPMDOC.M200B8C3 or CAPMSOC.M200B8C3nkmtbh
CAP_OC_CANCELLEDACCUMULATIONINT8Shows the number of CAP operations cancelled due to timer expirations on different levels, during the measurement period.CAPMDOC.M200B8C5 or CAPMSOC.M200B8C5nkmtbh
CAP_OC_ERRORSACCUMULATIONINT8Shows the number of CAP operations terminated by an error during the measurement period.CAPMDOC.M200B8C2 or CAPMSOC.M200B8C2nkmtbh
CAP_OC_REJECTEDACCUMULATIONINT8Shows the rejected CAP operations during the measurement period. It can be rejected by the TCAP user of the remote end, by the TCAP of the remote end, or by the near end TCAP.CAPMDOC.M200B8C4 or CAPMSOC.M200B8C4nkmtbh
CAP_OC_STARTEDACCUMULATIONINT8Shows the number of started CAP operations during the measurement period.CAPMDOC.M200B8C1 or CAPMSOC.M200B8C1nkmtbh


CDS Performance Indicators

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


CDS.Nokia.GSM.Control_Unit

Contains information about the number of seizures, successful calls, and congestion in that control unit.N.B. There is a secondary key of control_unit

The performance data measurements for this KPI group are recorded against the combination of CDS and Control_Unit (control_unit_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
cntl_accepACCUMULATIONINT8Number of successful call attempts (0...999999999), clear codes 0...3FF. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the call is ended by clear code 0...3FF.CNTLC.M18B2C3nkcdstbh
cntl_answACCUMULATIONINT8The number of call attempts (0...999999999) that have reached the conversation state. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the BSSAP CONNECT message is received from the BSC or the ISUP ANSWER message is received from the exchange.CNTLC.M18B2C5nkcdstbh
cntl_callsACCUMULATIONINT8Number of call attempts (0...999999999). The field is updated when the circuit is released. The counter is updated: during the following events: receiving the BSSAP RELEASE COMPLETE message from the BSC. receiving the RANAP Iu RELEASE COMPLETE message from the RNS.CNTLC.M18B2C2nkcdstbh
cntl_efailACCUMULATIONINT8Number of call attempts (0...999999999) that have terminated in a trunk circuit error, clear codes 800...BFF. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the call is ended by clear code 800...BFF.CNTLC.M18B2C8nkcdstbh
cntl_erlangsERLANGFLOATThe amount of traffic handled by the control unit in erlangs (0.0...9999.9). That means the total reservation time of the object being measured in relation to the results accumulation period. The erlangs are calculated from circuit seizure to circuit release.CNTLC.M18B2C9nkcdstbh
cntl_ifailACCUMULATIONINT8Number of call attempts (0...999999999) that have terminated in an error in the home exchange, clear codes 400...7FF. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the call is ended by clear code 400...7FF.CNTLC.M18B2C7nkcdstbh
cntl_invalid_recordINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid.CNTLC.M18B2C10nkcdstbh
cntl_sfailACCUMULATIONINT8Number of call attempts (0...999999999) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the call is ended by clear code C0...FFF.CNTLC.M18B2C6nkcdstbh
numdest_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when data provider in signalling unit or signalling unit(s) is restarted during the period and data might not be reliable.CNTLC.M18B2C11nkcdstbh


CDS.Nokia.GSM.IWF

The IWF measurement measures the usage of the IWF capacity and radio resources in data calls. N.B. There is a secondary key of call_type

The performance data measurements for this KPI group are recorded against the combination of CDS and Call_Type (call_type_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
iwf_calltype_answACCUMULATIONINT8Number of call attempts (0...999999) that have been answered. CODING: DWIWC.M311B2C2nkcdstbh
iwf_calltype_callsACCUMULATIONINT8Number of call attempts (0...999999) that have ended in the measurement period. CODING: DWIWC.M311B2C1nkcdstbh
iwf_calltype_failACCUMULATIONINT8Number of failed call attempts where the failure has been in IWF. CODING: DWIWC.M311B2C3nkcdstbh
iwf_calltype_onlineACCUMULATIONINT8Number of successful synchronisations between data terminals (0...999999). This counter indicates the amount of connections where the user data may have been transmitted. CODING: DWIWC.M311B2C4nkcdstbh
iwf_calltype_seizureINTENSITYFLOATTraffic intensity (0.0...999999.9) is the amount of total reservation time divided by the length of the measurement period. Total reservation time is measured in seconds from the reservation and the release of internal data circuits by call type. CODING: DW (value is multiplied by 100) NSS Statistics, ReportsIWC.M311B2C5nkcdstbh


CDS_Termination_Point Performance Indicators

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


CDS_Termination_Point.Nokia.GSM.Status

Circuit status

KPITypeData TypeDescriptionDerivationAdditional Summaries
CISE_STATE_0_FREE_FF_RESERVEDINTENSITYINT8State of the circuit (PCM-TSL) during the supervision period.CRCDT.M144B2C3nkcdstbh


Cell Performance Indicators

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


Cell.Nokia.GSM.MSC_Cell_Handovers_NBSC

This section describes the counters of M337: MeO MSC / MCCM / MNCM / LAC / CI.

KPITypeData TypeDescriptionDerivationAdditional Summaries
from_neighbour_cell_nokACCUMULATIONINT8Unsuccessful handovers from adjacent cell/SAHO2LAC.M337B4C8 
from_neighbour_cell_okACCUMULATIONINT8Successful handovers from adjacent cell/SAHO2LAC.M337B4C7 
intra_cell_okACCUMULATIONINT8Number of successful intra-cell handoversHO2LAC.M337B3C5 
toneighbourcellnokACCUMULATIONINT8Unsuccessful handovers to adjacent cell/SAHO2LAC.M337B4C6 
toneighbourcellokACCUMULATIONINT8Successful handovers to adjacent cell/SAHO2LAC.M337B4C5 


Cell.Nokia.GSM.MSC_Cell

This measurement contains the cell specific measurement results.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cellmeas_invalid_record_foundINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid.CELLCI.M22B4C13 
estab_callsACCUMULATIONINT8The total number of established callsCELLCI.M22B4C12 
mob_orig_bidACCUMULATIONINT8Mobile originating bids.CELLCI.M22B4C4 
mob_orig_estab_bidACCUMULATIONINT8Mobile originating established calls.CELLCI.M22B4C10 
mob_orig_succ_bidACCUMULATIONINT8Mobile originating successful bids.CELLCI.M22B4C7 
mob_term_bidACCUMULATIONINT8Mobile terminating bids.CELLCI.M22B4C5 
mob_term_estab_bidACCUMULATIONINT8Mobile terminating established calls.CELLCI.M22B4C11 
mob_term_succ_bidACCUMULATIONINT8Mobile terminating successful bids.CELLCI.M22B4C8 
succ_bidsACCUMULATIONINT8The total number of successful bids.CELLCI.M22B4C9 
tot_bidsACCUMULATIONINT8The total number of bids.CELLCI.M22B4C6 


Cell.Nokia.GSM.MSC_Handover_Cell

This table contains the location area specific part of the measurement results of the VLR measurement.

KPITypeData TypeDescriptionDerivationAdditional Summaries
fromneighbourcellnokACCUMULATIONINT8Unsuccessful handovers from adjacent cell/SAHO2CI.M337B4C8 
fromneighbourcellokACCUMULATIONINT8Successful handovers from adjacent cell/SAHO2CI.M337B4C7 
intra_cell_okACCUMULATIONINT8Number of successful intra-cell handoversHO2CI.M337B3C5 
succ_to_adjac_cell_hoACCUMULATIONINT8The number of unsuccessful handovers to the adjacent cell.HO2CI.M337B4C5 
toneighbourcellnokACCUMULATIONINT8Unsuccessful handovers to adjacent cell/SAHO2CI.M337B4C6 


Computer_Unit Performance Indicators

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


Computer_Unit.Nokia.GSM.SIP_Protocol

SIP Protocol related statistics

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIP_PROT_DATA_PROV_RESTARTINTENSITYINT8Indicates that a signalling unit or data provider program block inside has been restarted during the measured period, and that the presented counter values are not fully reliable.SIPPUNIT.M360B2C1 
SIP_PROT_NO_RESPONSEINTENSITYINT8Indicates that a signalling unit is down or does not respond for some reason during data collecting phase.SIPPUNIT.M360B2C2 


Computer_Unit.Nokia.GSM.TCP_Connection

TCP Connections

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIP_TCP_AVG_NUM_CONNECTIONSINTENSITYINT8Shows the average number of TCP connections during the RAP. The value presented in this counter is the sum of TCP connections at sampling divided by the samples number amount within the given time period.SIPPUNIT.M360B12C3 
SIP_TCP_DATA_PROV_RESTARTINTENSITYINT8Indicates that a signalling unit or data provider program block has been restarted inside it during the measured period, and the presented counter values are not fully reliable.SIPPUNIT.M360B12C1 
SIP_TCP_MAX_NUM_CONNECTIONSINTENSITYINT8Shows the peak value of TCP connections during the RAP.SIPPUNIT.M360B12C4 
SIP_TCP_NO_RESPONSEINTENSITYINT8Indicates that a signalling unit is down or does not respond for some reason during data collecting phase.SIPPUNIT.M360B12C2 


D_Link Performance Indicators

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


D_Link.Nokia.GSM.Error

This LAPD measurement is used to collect data on the Q.921 error functions of the LAPD connections

KPITypeData TypeDescriptionDerivationAdditional Summaries
disc_failACCUMULATIONINT8Unsuccessful retransmission of DISC (cntr H).LAPEM.M223B2C7nkdlttbh, nkmtbh
dm_f0ACCUMULATIONINT8Receipt of unsolicited DM, F=0 (cntr E).LAPEM.M223B2C1nkdlttbh, nkmtbh
dm_f1ACCUMULATIONINT8Receipt of unsolicited DM, F=1 (cntr B).LAPEM.M223B2C2nkdlttbh, nkmtbh
frame_size_failACCUMULATIONINT8Receipt of frame with wrong size (cntr N).LAPEM.M223B2C12nkdlttbh, nkmtbh
frmr_responseACCUMULATIONINT8Receipt of FRMR response (cntr K).LAPEM.M223B2C9nkdlttbh, nkmtbh
i_field_not_permittedACCUMULATIONINT8Receipt of I field not permitted (cntr M).LAPEM.M223B2C11nkdlttbh, nkmtbh
n201_errorACCUMULATIONINT8N201 error (cntr O).LAPEM.M223B2C15nkdlttbh, nkmtbh
non_implemented_frameACCUMULATIONINT8Receipt of non-implemented frame (cntr L).LAPEM.M223B2C10nkdlttbh, nkmtbh
nr_failACCUMULATIONINT8N(R) error (cntr J).LAPEM.M223B2C14nkdlttbh, nkmtbh
peer_re_establishedACCUMULATIONINT8Peer initiated re-establishment (cntr F).LAPEM.M223B2C13nkdlttbh, nkmtbh
rr_f1ACCUMULATIONINT8Receipt of unsolicited RR/RNR/REJ, F=1 (cntr A).LAPEM.M223B2C5nkdlttbh, nkmtbh
sabme_failACCUMULATIONINT8Unsuccessful retransmission of SABME (cntr G).LAPEM.M223B2C6nkdlttbh, nkmtbh
stat_inquiry_failACCUMULATIONINT8Unsuccessful retransmission of status inquiry (cntr I).LAPEM.M223B2C8nkdlttbh, nkmtbh
ua_f0ACCUMULATIONINT8Receipt of unsolicited UA, F=0 (cntr D).LAPEM.M223B2C4nkdlttbh, nkmtbh
ua_f1ACCUMULATIONINT8Receipt of unsolicited UA, F=1 (cntr C).LAPEM.M223B2C3nkdlttbh, nkmtbh


D_Link.Nokia.GSM.Traffic

This LAPD measurement is used to collect data on the traffic of the LAPD connections. This data shows any overload or failure situations on the LAPD connections.

KPITypeData TypeDescriptionDerivationAdditional Summaries
received_i_framesACCUMULATIONINT8Received I frames.LAPDM.M221B2C2nkdlttbh, nkmtbh
received_i_octetsACCUMULATIONINT8Received I frame octets.LAPDM.M221B2C6nkdlttbh, nkmtbh
received_total_octetsACCUMULATIONINT8Received total octet count.LAPDM.M221B2C10nkdlttbh, nkmtbh
received_ui_framesACCUMULATIONINT8Received UI frames.LAPDM.M221B2C4nkdlttbh, nkmtbh
received_ui_octetsACCUMULATIONINT8Received UI frame octets.LAPDM.M221B2C8nkdlttbh, nkmtbh
total_octetsACCUMULATIONINT8Total transmitted and received octets.{trans_total_octets} + {received_total_octets}nkdlttbh, nkmtbh
trans_i_framesACCUMULATIONINT8Transmitted I frames.LAPDM.M221B2C1nkdlttbh, nkmtbh
trans_i_octetsACCUMULATIONINT8Transmitted I frame octets.LAPDM.M221B2C5nkdlttbh, nkmtbh
trans_total_octetsACCUMULATIONINT8Transmitted total octet count.LAPDM.M221B2C9nkdlttbh, nkmtbh
trans_ui_framesACCUMULATIONINT8Transmitted UI frames.LAPDM.M221B2C3nkdlttbh, nkmtbh
trans_ui_octetsACCUMULATIONINT8Transmitted UI frame octets.LAPDM.M221B2C7nkdlttbh, nkmtbh


D_Link.Nokia.GSM.Utilisation

The LAPD measurements are used to collect data on the utilisation of the LAPD connections. This data shows any overload or failure situations on the LAPD connections.

KPITypeData TypeDescriptionDerivationAdditional Summaries
clock_signal_missingACCUMULATIONINT8Clock signal missing messages.LAPUM.M222B2C11nkdlttbh, nkmtbh
crc_errorsACCUMULATIONINT8CRC errors.LAPUM.M222B2C5nkdlttbh, nkmtbh
dl_data_indACCUMULATIONINT8The number of DL-DATA-INDICATIONS.LAPUM.M222B2C2nkdlttbh, nkmtbh
dl_data_req_deletedACCUMULATIONINT8Deleted DL-DATA-REQUESTS.LAPUM.M222B2C7nkdlttbh, nkmtbh
dl_data_reqACCUMULATIONINT8The number of DL-DATA-REQUESTS.LAPUM.M222B2C1nkdlttbh, nkmtbh
dl_data_unit_indACCUMULATIONINT8The number of DL-UNIT-DATA-INDICATIONS.LAPUM.M222B2C4nkdlttbh, nkmtbh
dl_data_unit_reqACCUMULATIONINT8The number of DL-UNIT-DATA-REQUESTS.LAPUM.M222B2C3nkdlttbh, nkmtbh
dmc_overflowsACCUMULATIONINT8DMC message buffer overflows.LAPUM.M222B2C10nkdlttbh, nkmtbh
frame_errorsACCUMULATIONINT8Frame errors.LAPUM.M222B2C6nkdlttbh, nkmtbh
i_frames_deletedACCUMULATIONINT8Deleted I frames in the window.LAPUM.M222B2C8nkdlttbh, nkmtbh
t200_expiryACCUMULATIONINT8T200 expiries.LAPUM.M222B2C9nkdlttbh, nkmtbh


EIR_IMEI Performance Indicators

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


EIR_IMEI.Nokia.GSM.EIR

EIR measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
regtypeisglobal_if_value_is_1INTENSITYINTEGERThe allowed value for this counter is 1. If counter is sent in XML report with respective value, it means that the registration type of device is GLOBAL.EIRI.M85B5C1nkhlrsubbh
regtypeislocal_if_value_is_1INTENSITYINTEGERThe allowed value for this counter is 1. If counter is sent in XML report with respective value, it means that the registration type of device is LOCAL.EIRI.M85B5C0nkhlrsubbh
req_for_duplicated_eqACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is (POSSIBLY) DUPLICATED - this IMEI (possibly) has been copied into several different mobiles If IMEI belongs to black list then the reason code is DUPLICATED If IMEI belongs to grey list then the reason code is POSSIBLY DUPLICATEDEIRI.M85B6C16nkhlrsubbh
req_for_impersonated_eqACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is (POSSIBLY) IMPERSONATED - this IMEI is (possibly) not corresponding to the white list, it is (possibly) illegally issued and not provided by the manufacturer, operator, or a type of approval house. If IMEI belongs to black list then the reason code is IMPERSONATED If IMEI belongs to grey list then the reason code is POSSIBLY IMPERSONATEDEIRI.M85B6C17nkhlrsubbh
req_for_other_reasonACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is some otherEIRI.M85B6C99nkhlrsubbh
req_for_pos_illegal_eqACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is (POSSIBLY) ILLEGAL - the device is (possibly) illegal. If IMEI belongs to black list then the reason code is ILLEGAL If IMEI belongs to grey list then reason code is POSSIBLY ILLEGALEIRI.M85B6C12nkhlrsubbh
req_for_pos_not_prop_work_eqACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is (POSSIBLY) NOT WORKING - the device is (possibly) out of order. If IMEI belongs to black list then the reason code is NOT WORKING. If IMEI belongs to grey list then the reason code is POSSIBLY NOT WORKINGEIRI.M85B6C10nkhlrsubbh
req_for_stolen_eqACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is STOLEN - the device is stolen. If the reason code is STOLEN, IMEI always belongs to black list.EIRI.M85B6C11nkhlrsubbh
REQUESTS_THIRD_PARTY_LISTINGACCUMULATIONINT8Shows the number of IMEI requests for those devices whose reason code is THIRD PARTY LISTING REQUEST. If IMEI can belong to black list only.EIRI.M85B6C23nkhlrsubbh
REQUESTS_UNSPECIFIEDACCUMULATIONINT8Shows the number of IMEI requests for those devices whose reason code is UNSPECIFIED. This means that the IMEI has been migrated to IMEI Database from the CEIR system. IMEI can belong to black list and grey list too.EIRI.M85B6C25nkhlrsubbh
requestsACCUMULATIONINT8The number of IMEI requests for those devices whose reason code is NEW - new device. If the reason code is NEW, the IMEI always belongs to grey list.EIRI.M85B6C4nkhlrsubbh


Exchange_Terminal Performance Indicators

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


Exchange_Terminal.Nokia.GSM.HLR_PCM_AIS_Received

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to AIS Received counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_ais_received1ACCUMULATIONINT8AIS received counter 1.ETH.M145B2C21 
dtb_ais_received2ACCUMULATIONINT8AIS received counter 2.ETH.M145B2C22 
dtb_ais_received3ACCUMULATIONINT8AIS received counter 3.ETH.M145B2C23 
dtb_ais_received4ACCUMULATIONINT8AIS received counter 4.ETH.M145B2C24 


Exchange_Terminal.Nokia.GSM.HLR_PCM_CRC

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to CRC counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
crc_time_localACCUMULATIONINT8CRC measurement: total time at local end, given in 1/100 seconds.ETH.M145B2C62 
crc_time_nt1_refACCUMULATIONINT8CRC measurement: total time at NT1 T reference point, given in 1/100 seconds.ETH.M145B2C78 
crc_time_remoteACCUMULATIONINT8CRC measurement: total time at remote end, given in 1/100 seconds.ETH.M145B2C70 
crc_time_teACCUMULATIONINT8CRC measurement: total time at TE, given in 1/100 seconds.ETH.M145B2C85 
et_crc_error_codeINTENSITYINTEGERError code concerning the CRC counters. Zero value means a successful report, nonzero value indicates that no CRC counters are present. The value is a general DX error code in decimal format.ETH.M145B2C5 


Exchange_Terminal.Nokia.GSM.HLR_PCM_Degrade_Service

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to degrade service counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
bg_error_localACCUMULATIONINT8Background block errors of local end. ETH.M145B2C69 
bg_error_remoteACCUMULATIONINT8Background block errors of remote end. ETH.M145B2C77 
degraded_minutes_localACCUMULATIONINT8Degraded minutes.ETH.M145B2C65 
degraded_minutes_nt1ACCUMULATIONINT8Degraded minutes of NT1. ETH.M145B2C81 
degraded_minutes_remoteACCUMULATIONINT8Degraded minutes of the remote end.ETH.M145B2C73 
degraded_minutes_teACCUMULATIONINT8Degraded minutes of TE. ETH.M145B2C88 
error_seconds_localACCUMULATIONINT8Errored seconds.ETH.M145B2C66 
error_seconds_nt1ACCUMULATIONINT8Errored seconds of NT1. ETH.M145B2C82 
error_seconds_remoteACCUMULATIONINT8Errored seconds of the remote end.ETH.M145B2C74 
error_seconds_teACCUMULATIONINT8Errored seconds of TE. ETH.M145B2C89 
errored_seconds_localACCUMULATIONINT8Seriously errored seconds.ETH.M145B2C68 
errored_seconds_nt1ACCUMULATIONINT8Seriously errored seconds of NT1. ETH.M145B2C84 
errored_seconds_remoteACCUMULATIONINT8Seriously errored seconds of the remote end.ETH.M145B2C76 
errored_seconds_teACCUMULATIONINT8Seriously errored seconds of TE. ETH.M145B2C91 


Exchange_Terminal.Nokia.GSM.HLR_PCM_Disturbance

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Specifically disturbance counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_ais_from_et1ACCUMULATIONINT8Disturbance counters: AIS received counter1. ETH.M145B2C45 
dtb_ais_from_et2ACCUMULATIONINT8Disturbance counters: AIS received counter2. ETH.M145B2C46 
dtb_ais_from_et3ACCUMULATIONINT8Disturbance counters: AIS received counter3. ETH.M145B2C47 
dtb_ais_from_et4ACCUMULATIONINT8Disturbance counters: AIS received counter4. ETH.M145B2C48 
dtb_err_v3_loopback1ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter1. ETH.M145B2C29 
dtb_err_v3_loopback2ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter2. ETH.M145B2C30 
dtb_err_v3_loopback3ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter3. ETH.M145B2C31 
dtb_err_v3_loopback4ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter4. ETH.M145B2C32 
dtb_limit1_lowerINTENSITYINTEGERLower limit for disturbance counter 1.ETH.M145B2C6 
dtb_limit1_upperINTENSITYINTEGERUpper limit for disturbance counter 1.ETH.M145B2C7 
dtb_limit2_lowerINTENSITYINTEGERLower limit for disturbance counter 2.ETH.M145B2C8 
dtb_limit2_upperINTENSITYINTEGERUpper limit for disturbance counter 2.ETH.M145B2C9 
dtb_limit3_lowerINTENSITYINTEGERLower limit for disturbance counter 3.ETH.M145B2C10 
dtb_limit3_upperINTENSITYINTEGERUpper limit for disturbance counter 3.ETH.M145B2C11 
dtb_limit4_lowerINTENSITYINTEGERLower limit for disturbance counter 4.ETH.M145B2C12 
dtb_nt1_lost_power1ACCUMULATIONINT8Disturbance counters: NT1 power lost counter1. ETH.M145B2C41 
dtb_nt1_lost_power2ACCUMULATIONINT8Disturbance counters: NT1 power lost counter2. ETH.M145B2C42 
dtb_nt1_lost_power3ACCUMULATIONINT8Disturbance counters: NT1 power lost counter3. ETH.M145B2C43 
dtb_nt1_lost_power4ACCUMULATIONINT8Disturbance counters: NT1 power lost counter4. ETH.M145B2C44 
dtb_nt1_lost_signal1ACCUMULATIONINT8Disturbance counters: NT1 lost signal from ET count1. ETH.M145B2C37 
dtb_nt1_lost_signal2ACCUMULATIONINT8The number of NT1 lost signal or frame alignment disturbances of group 2.ETH.M145B2C38 
dtb_nt1_lost_signal3ACCUMULATIONINT8Disturbance counters: NT1 lost signal from ET count3. ETH.M145B2C39 
dtb_nt1_lost_signal4ACCUMULATIONINT8The number of NT1 lost signal or frame alignment disturbances of group 4.ETH.M145B2C40 
dtb_nt1_lost1ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count1. ETH.M145B2C33 
dtb_nt1_lost2ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count2. ETH.M145B2C34 
dtb_nt1_lost3ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count3. ETH.M145B2C35 
dtb_nt1_lost4ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count4. ETH.M145B2C36 
et_dist_error_codeINTENSITYINTEGERError code concerning the short disturbances counters. Zero value means a successful report, nonzero value indicates that no disturbance counters are present. The value is a general DX error code in decimal format.ETH.M145B2C2 


Exchange_Terminal.Nokia.GSM.HLR_PCM_Frame_Alignment

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to Frame Alignment counters.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_frame_alignment_lost1ACCUMULATIONINT8Frame alignment lost counter 1.ETH.M145B2C17 
dtb_frame_alignment_lost2ACCUMULATIONINT8Frame alignment lost counter 2.ETH.M145B2C18 
dtb_frame_alignment_lost3ACCUMULATIONINT8Frame alignment lost counter 3.ETH.M145B2C19 
dtb_frame_alignment_lost4ACCUMULATIONINT8Frame alignment lost counter 4.ETH.M145B2C20 
et_fra_error_codeINTENSITYINTEGERError code concerning the frame alignment error counters. Zero value means a successful report, nonzero value indicates that no frame alignment counters are present. The value is a general DX error code in decimal format.ETH.M145B2C3 
fa_frame_alignment_lost1ACCUMULATIONINT8Frame alignment lost counters: Frame counter 1.ETH.M145B2C56 
fa_frame_alignment_lost2ACCUMULATIONINT8Frame alignment lost counters: Frame counter 2.ETH.M145B2C57 
fa_frame_alignment_lost3ACCUMULATIONINT8Frame alignment lost counters: Frame counter 3.ETH.M145B2C58 
fa_frame_alignment_lost4ACCUMULATIONINT8Frame alignment lost counters: Frame counter 4.ETH.M145B2C59 
fa_limits1_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 1 lower.ETH.M145B2C49 
fa_limits1_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 1 upper.ETH.M145B2C50 
fa_limits2_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 2 lower.ETH.M145B2C51 
fa_limits2_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 2 upper.ETH.M145B2C52 
fa_limits3_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 3 lower.ETH.M145B2C53 
fa_limits3_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 3 upper.ETH.M145B2C54 
fa_limits4_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 4 lower.ETH.M145B2C55 


Exchange_Terminal.Nokia.GSM.HLR_PCM_Signal_Missing

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to Signal missing counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_sig_errors1ACCUMULATIONINT8The number of incoming signal missing disturbances of group 1.ETH.M145B2C13 
dtb_sig_errors2ACCUMULATIONINT8The number of incoming signal missing disturbances of group 2.ETH.M145B2C14 
dtb_sig_errors3ACCUMULATIONINT8The number of incoming signal missing disturbances of group 3.ETH.M145B2C15 
dtb_sig_errors4ACCUMULATIONINT8The number of incoming signal missing disturbances of group 4.ETH.M145B2C16 


Exchange_Terminal.Nokia.GSM.HLR_PCM_Statistics

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period.

KPITypeData TypeDescriptionDerivationAdditional Summaries
avail_time_localACCUMULATIONINT8Availability time ETH.M145B2C63 
avail_time_nt1_refACCUMULATIONINT8Availability time NT1 REF P ETH.M145B2C79 
avail_time_remoteACCUMULATIONINT8Availability time of the remote end ETH.M145B2C71 
avail_time_teACCUMULATIONINT8Availability time TE ETH.M145B2C86 
dtb_remote_alarm1ACCUMULATIONINT8Remote end alarm counter 1.ETH.M145B2C25 
dtb_remote_alarm2ACCUMULATIONINT8Remote end alarm counter 2.ETH.M145B2C26 
dtb_remote_alarm3ACCUMULATIONINT8Remote end alarm counter 3.ETH.M145B2C27 
dtb_remote_alarm4ACCUMULATIONINT8Remote end alarm counter 4.ETH.M145B2C28 
error_free_seconds_localACCUMULATIONINT8Error free seconds.ETH.M145B2C67 
error_free_seconds_nt1ACCUMULATIONINT8Error free seconds of NT1. ETH.M145B2C83 
error_free_seconds_remoteACCUMULATIONINT8Error free seconds of the remote end.ETH.M145B2C75 
error_free_seconds_teACCUMULATIONINT8Error free seconds of TE. ETH.M145B2C90 
et_slip_error_codeINTENSITYINTEGERError code concerning the slip counters. Zero value means a successful report, nonzero value indicates that no slip counters are present. The value is a general DX error code in decimal format.ETH.M145B2C4 
et_total_error_codeINTENSITYINTEGERError code concerning the whole report. Zero value means a successful report, nonzero value indicates that no counters are present. The value is a general DX error code in decimal format.ETH.M145B2C1 
slip_negativeACCUMULATIONINT8Counter value for negative slips.ETH.M145B2C60 
slip_positiveACCUMULATIONINT8Counter value for positive slips.ETH.M145B2C61 
unavail_time_localACCUMULATIONINT8Unavailability time ETH.M145B2C64 
unavail_time_nt1_refACCUMULATIONINT8Unavailability time NT1 REF P ETH.M145B2C80 
unavail_time_remoteACCUMULATIONINT8Unavailability time of the remote endETH.M145B2C72 
unavail_time_teACCUMULATIONINT8Unavailability time TE ETH.M145B2C87 


Exchange_Terminal.Nokia.GSM.MSC_PCM_AIS_Received

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to AIS Received counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_ais_received1ACCUMULATIONINT8AIS received counter 1.ETM.M145B2C21nkmtbh
dtb_ais_received2ACCUMULATIONINT8AIS received counter 2.ETM.M145B2C22nkmtbh
dtb_ais_received3ACCUMULATIONINT8AIS received counter 3.ETM.M145B2C23nkmtbh
dtb_ais_received4ACCUMULATIONINT8AIS received counter 4.ETM.M145B2C24nkmtbh


Exchange_Terminal.Nokia.GSM.MSC_PCM_CRC

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to CRC counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
crc_time_localACCUMULATIONINT8(Obsolete in M13.5) Total time that the CRC statistics has been on ETM.obsoletenkmtbh
crc_time_nt1_refACCUMULATIONINT8(Obsolete in M13.5) Total time CRC at NT1 REF P ETM.obsoletenkmtbh
crc_time_remoteACCUMULATIONINT8(Obsolete in M13.5) Total time that the CRC statistics has been on at the remote end ETM.obsoletenkmtbh
crc_time_teACCUMULATIONINT8(Obsolete in M13.5) Total time CRC at TE ETM.obsoletenkmtbh
et_crc_error_codeINTENSITYINT8Error code concerning the CRC counters. Zero value means a successful report, nonzero value indicates that no CRC counters are present. The value is a general DX error code in decimal format.ETM.M145B2C5nkmtbh
et_local_end_avail_timeINTENSITYINT8CRC measurement: availability time at local end, given in 1/100 seconds.ETM.M145B2C63nkmtbh
et_local_end_total_timeINTENSITYINT8CRC measurement: total time at local end, given in 1/100 seconds.ETM.M145B2C62nkmtbh
et_nt1_t_avail_timeINTENSITYINT8CRC measurement: availability time at NT1 T reference point, given in 1/100 seconds.ETM.M145B2C79nkmtbh
et_nt1_t_total_timeINTENSITYINT8CRC measurement: total time at NT1 T reference point, given in 1/100 seconds.ETM.M145B2C78nkmtbh
et_nt1_t_unavail_timeINTENSITYINT8CRC measurement: unavailability time at NT1 T reference point, given in 1/100 seconds.ETM.M145B2C80nkmtbh
et_remote_end_avail_timeINTENSITYINT8CRC measurement: availability time at remote end, given in 1/100 seconds.ETM.M145B2C71nkmtbh
et_remote_end_total_timeINTENSITYINT8CRC measurement: total time at remote end, given in 1/100 seconds.ETM.M145B2C70nkmtbh
et_te_avail_timeINTENSITYINT8CRC measurement: availability time at TE, given in 1/100 seconds.ETM.M145B2C86nkmtbh
et_te_total_timeINTENSITYINT8CRC measurement: total time at TE, given in 1/100 seconds.ETM.M145B2C85nkmtbh
et_te_unavail_timeINTENSITYINT8CRC measurement: unavailability time at TE, given in 1/100 seconds.ETM.M145B2C87nkmtbh


Exchange_Terminal.Nokia.GSM.MSC_PCM_Degrade_Service

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to degrade service counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
bg_error_localACCUMULATIONINT8Background block errors of local end. ETM.M145B2C69nkmtbh
bg_error_remoteACCUMULATIONINT8Background block errors of remote end. ETM.M145B2C77nkmtbh
degraded_minutes_localACCUMULATIONINT8Degraded minutes.ETM.M145B2C65nkmtbh
degraded_minutes_nt1ACCUMULATIONINT8Degraded minutes of NT1. ETM.M145B2C81nkmtbh
degraded_minutes_remoteACCUMULATIONINT8Degraded minutes of the remote end.ETM.M145B2C73nkmtbh
degraded_minutes_teACCUMULATIONINT8Degraded minutes of TE. ETM.M145B2C88nkmtbh
error_seconds_localACCUMULATIONINT8Errored seconds.ETM.M145B2C66nkmtbh
error_seconds_nt1ACCUMULATIONINT8Errored seconds of NT1. ETM.M145B2C82nkmtbh
error_seconds_remoteACCUMULATIONINT8Errored seconds of the remote end.ETM.M145B2C74nkmtbh
error_seconds_teACCUMULATIONINT8Errored seconds of TE. ETM.M145B2C89nkmtbh
errored_seconds_localACCUMULATIONINT8Seriously errored seconds.ETM.M145B2C68nkmtbh
errored_seconds_nt1ACCUMULATIONINT8Seriously errored seconds of NT1. ETM.M145B2C84nkmtbh
errored_seconds_remoteACCUMULATIONINT8Seriously errored seconds of the remote end.ETM.M145B2C76nkmtbh
errored_seconds_teACCUMULATIONINT8Seriously errored seconds of TE. ETM.M145B2C91nkmtbh


Exchange_Terminal.Nokia.GSM.MSC_PCM_DTB_Disturbance

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to DTB disturbance counters.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_ais_from_et1ACCUMULATIONINT8Disturbance counters: AIS received counter1. ETM.M145B2C45nkmtbh
dtb_ais_from_et2ACCUMULATIONINT8Disturbance counters: AIS received counter2. ETM.M145B2C46nkmtbh
dtb_ais_from_et3ACCUMULATIONINT8Disturbance counters: AIS received counter3. ETM.M145B2C47nkmtbh
dtb_ais_from_et4ACCUMULATIONINT8Disturbance counters: AIS received counter4. ETM.M145B2C48nkmtbh
dtb_err_v3_loopback1ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter1. ETM.M145B2C29nkmtbh
dtb_err_v3_loopback2ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter2. ETM.M145B2C30nkmtbh
dtb_err_v3_loopback3ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter3. ETM.M145B2C31nkmtbh
dtb_err_v3_loopback4ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter4. ETM.M145B2C32nkmtbh
dtb_limit1_lowerINTENSITYINTEGERLower limit for disturbance counter 1.round(ETM.M145B2C6 / 1000, 0)nkmtbh
dtb_limit1_upperINTENSITYINTEGERUpper limit for disturbance counter 1.round(ETM.M145B2C7 / 1000, 0)nkmtbh
dtb_limit2_lowerINTENSITYINTEGERLower limit for disturbance counter 2.round(ETM.M145B2C8 / 1000, 0)nkmtbh
dtb_limit2_upperINTENSITYINTEGERUpper limit for disturbance counter 2.round(ETM.M145B2C9 / 1000, 0)nkmtbh
dtb_limit3_lowerINTENSITYINTEGERLower limit for disturbance counter 3.round(ETM.M145B2C10 / 1000, 0)nkmtbh
dtb_limit3_upperINTENSITYINTEGERUpper limit for disturbance counter 3.round(ETM.M145B2C11 / 1000, 0)nkmtbh
dtb_limit4_lowerINTENSITYINTEGERLower limit for disturbance counter 4.round(ETM.M145B2C12 / 1000, 0)nkmtbh
dtb_nt1_lost_power1ACCUMULATIONINT8Disturbance counters: NT1 power lost counter1. ETM.M145B2C41nkmtbh
dtb_nt1_lost_power2ACCUMULATIONINT8Disturbance counters: NT1 power lost counter2. ETM.M145B2C42nkmtbh
dtb_nt1_lost_power3ACCUMULATIONINT8Disturbance counters: NT1 power lost counter3. ETM.M145B2C43nkmtbh
dtb_nt1_lost_power4ACCUMULATIONINT8Disturbance counters: NT1 power lost counter4. ETM.M145B2C44nkmtbh
dtb_nt1_lost_signal1ACCUMULATIONINT8Disturbance counters: NT1 lost signal from ET count1. ETM.M145B2C37nkmtbh
dtb_nt1_lost_signal2ACCUMULATIONINT8The number of NT1 lost signal or frame alignment disturbances of group 2.ETM.M145B2C38nkmtbh
dtb_nt1_lost_signal3ACCUMULATIONINT8Disturbance counters: NT1 lost signal from ET count3. ETM.M145B2C39nkmtbh
dtb_nt1_lost_signal4ACCUMULATIONINT8The number of NT1 lost signal or frame alignment disturbances of group 4.ETM.M145B2C40nkmtbh
dtb_nt1_lost1ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count1. ETM.M145B2C33nkmtbh
dtb_nt1_lost2ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count2. ETM.M145B2C34nkmtbh
dtb_nt1_lost3ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count3. ETM.M145B2C35nkmtbh
dtb_nt1_lost4ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count4. ETM.M145B2C36nkmtbh
et_dist_error_codeINTENSITYINTEGERError code concerning the short disturbances counters. Zero value means a successful report, nonzero value indicates that no disturbance counters are present. The value is a general DX error code in decimal format.ETM.M145B2C2nkmtbh


Exchange_Terminal.Nokia.GSM.MSC_PCM_Frame_Alignment

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to Frame Alignment counters.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_frame_alignment_lost1ACCUMULATIONINT8Frame alignment lost counter 1.ETM.M145B2C17nkmtbh
dtb_frame_alignment_lost2ACCUMULATIONINT8Frame alignment lost counter 2.ETM.M145B2C18nkmtbh
dtb_frame_alignment_lost3ACCUMULATIONINT8Frame alignment lost counter 3.ETM.M145B2C19nkmtbh
dtb_frame_alignment_lost4ACCUMULATIONINT8Frame alignment lost counter 4.ETM.M145B2C20nkmtbh
et_fra_error_codeINTENSITYINTEGERError code concerning the frame alignment error counters. Zero value means a successful report, nonzero value indicates that no frame alignment counters are present. The value is a general DX error code in decimal format.ETM.M145B2C3nkmtbh
fa_frame_alignment_lost1ACCUMULATIONINT8Frame alignment lost counters: Frame counter 1.ETM.M145B2C56nkmtbh
fa_frame_alignment_lost2ACCUMULATIONINT8Frame alignment lost counters: Frame counter 2.ETM.M145B2C57nkmtbh
fa_frame_alignment_lost3ACCUMULATIONINT8Frame alignment lost counters: Frame counter 3.ETM.M145B2C58nkmtbh
fa_frame_alignment_lost4ACCUMULATIONINT8Frame alignment lost counters: Frame counter 4.ETM.M145B2C59nkmtbh
fa_limits1_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 1 lower.ETM.M145B2C49nkmtbh
fa_limits1_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 1 upper.ETM.M145B2C50nkmtbh
fa_limits2_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 2 lower.ETM.M145B2C51nkmtbh
fa_limits2_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 2 upper.ETM.M145B2C52nkmtbh
fa_limits3_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 3 lower.ETM.M145B2C53nkmtbh
fa_limits3_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 3 upper.ETM.M145B2C54nkmtbh
fa_limits4_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 4 lower.ETM.M145B2C55nkmtbh


Exchange_Terminal.Nokia.GSM.MSC_PCM_Signal_Missing

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period. Related to Signal missing counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_sig_errors1ACCUMULATIONINT8The number of incoming signal missing disturbances of group 1.ETM.M145B2C13nkmtbh
dtb_sig_errors2ACCUMULATIONINT8Signal missing counter 2.ETM.M145B2C14nkmtbh
dtb_sig_errors3ACCUMULATIONINT8The number of incoming signal missing disturbances of group 3.ETM.M145B2C15nkmtbh
dtb_sig_errors4ACCUMULATIONINT8Signal missing counter 4.ETM.M145B2C16nkmtbh


Exchange_Terminal.Nokia.GSM.MSC_PCM_Statistics

This measurement deals with the statistical counters for trunk circuits and the values calculated from the beginning of a permanent measurement period.

KPITypeData TypeDescriptionDerivationAdditional Summaries
avail_time_localACCUMULATIONINT8Availability time ETM.obsoletenkmtbh
avail_time_nt1_refACCUMULATIONINT8Availability time NT1 REF P ETM.obsoletenkmtbh
avail_time_remoteACCUMULATIONINT8Availability time of the remote end ETM.obsoletenkmtbh
avail_time_teACCUMULATIONINT8Availability time TE ETM.obsoletenkmtbh
dtb_remote_alarm1ACCUMULATIONINT8Remote end alarm counter 1.ETM.M145B2C25nkmtbh
dtb_remote_alarm2ACCUMULATIONINT8Remote end alarm counter 2.ETM.M145B2C26nkmtbh
dtb_remote_alarm3ACCUMULATIONINT8Remote end alarm counter 3.ETM.M145B2C27nkmtbh
dtb_remote_alarm4ACCUMULATIONINT8Remote end alarm counter 4.ETM.M145B2C28nkmtbh
error_free_seconds_localACCUMULATIONINT8Error free seconds.ETM.M145B2C67nkmtbh
error_free_seconds_nt1ACCUMULATIONINT8Error free seconds of NT1. ETM.M145B2C83nkmtbh
error_free_seconds_remoteACCUMULATIONINT8Error free seconds of the remote end.ETM.M145B2C75nkmtbh
error_free_seconds_teACCUMULATIONINT8Error free seconds of TE. ETM.M145B2C90nkmtbh
et_slip_error_codeINTENSITYINTEGERError code concerning the slip counters. Zero value means a successful report, nonzero value indicates that no slip counters are present. The value is a general DX error code in decimal format.ETM.M145B2C4nkmtbh
et_total_error_codeINTENSITYINTEGERError code concerning the whole report. Zero value means a successful report, nonzero value indicates that no counters are present. The value is a general DX error code in decimal format.ETM.M145B2C1nkmtbh
slip_negativeACCUMULATIONINT8Counter value for negative slips.ETM.M145B2C60nkmtbh
slip_positiveACCUMULATIONINT8Counter value for positive slips.ETM.M145B2C61nkmtbh
unavail_time_localACCUMULATIONINT8Unavailability time ETM.M145B2C64nkmtbh
unavail_time_nt1_refACCUMULATIONINT8Unavailability time NT1 REF P ETM.obsoletenkmtbh
unavail_time_remoteACCUMULATIONINT8Unavailability time of the remote endETM.M145B2C72nkmtbh
unavail_time_teACCUMULATIONINT8Unavailability time TE ETM.obsoletenkmtbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_AIS_Received

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors. These relate to AIS received counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_ais_received1ACCUMULATIONINT8AIS received counter 1.ETS.M145B2C21nksrrotbh
dtb_ais_received2ACCUMULATIONINT8AIS received counter 2.ETS.M145B2C22nksrrotbh
dtb_ais_received3ACCUMULATIONINT8AIS received counter 3.ETS.M145B2C23nksrrotbh
dtb_ais_received4ACCUMULATIONINT8AIS received counter 4.ETS.M145B2C24nksrrotbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_CRC

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors. These relate to CRC counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
crc_time_localACCUMULATIONINT8Total time that the CRC statistics has been onETS.M145B2C62nksrrotbh
crc_time_nt1_refACCUMULATIONINT8Total time CRC at NT1 REF PETS.M145B2C78nksrrotbh
crc_time_remoteACCUMULATIONINT8Total time that the CRC statistics has been on at the remote endETS.M145B2C70nksrrotbh
crc_time_teACCUMULATIONINT8Total time CRC at TEETS.M145B2C85nksrrotbh
et_crc_error_codeINTENSITYINTEGERError code concerning the CRC counters. Zero value means a successful report, nonzero value indicates that no CRC counters are present. The value is a general DX error code in decimal format.ETS.M145B2C5nksrrotbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_Degrade_Service

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors. These relate to degrade service counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
bg_error_localACCUMULATIONINT8Background block errors of local end.ETS.M145B2C69nksrrotbh
bg_error_remoteACCUMULATIONINT8Background block errors of remote end.ETS.M145B2C77nksrrotbh
degraded_minutes_localACCUMULATIONINT8Degraded minutes.ETS.M145B2C65nksrrotbh
degraded_minutes_nt1ACCUMULATIONINT8Degraded minutes of NT1.ETS.M145B2C81nksrrotbh
degraded_minutes_remoteACCUMULATIONINT8Degraded minutes of the remote end.ETS.M145B2C73nksrrotbh
degraded_minutes_teACCUMULATIONINT8Degraded minutes of TE.ETS.M145B2C88nksrrotbh
error_seconds_localACCUMULATIONINT8Errored seconds.ETS.M145B2C66nksrrotbh
error_seconds_nt1ACCUMULATIONINT8Errored seconds of NT1.ETS.M145B2C82nksrrotbh
error_seconds_remoteACCUMULATIONINT8Errored seconds of the remote end.ETS.M145B2C74nksrrotbh
error_seconds_teACCUMULATIONINT8Errored seconds of TE.ETS.M145B2C89nksrrotbh
errored_seconds_localACCUMULATIONINT8Seriously errored seconds.ETS.M145B2C68nksrrotbh
errored_seconds_nt1ACCUMULATIONINT8Seriously errored seconds of NT1.ETS.M145B2C84nksrrotbh
errored_seconds_remoteACCUMULATIONINT8Seriously errored seconds of the remote end.ETS.M145B2C76nksrrotbh
errored_seconds_teACCUMULATIONINT8Seriously errored seconds of TE.ETS.M145B2C91nksrrotbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_Disturbance

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors. These relate to Disturbance counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_ais_from_et1ACCUMULATIONINT8Disturbance counters: AIS received counter1.ETS.M145B2C45nksrrotbh
dtb_ais_from_et2ACCUMULATIONINT8Disturbance counters: AIS received counter2.ETS.M145B2C46nksrrotbh
dtb_ais_from_et3ACCUMULATIONINT8Disturbance counters: AIS received counter3.ETS.M145B2C47nksrrotbh
dtb_ais_from_et4ACCUMULATIONINT8Disturbance counters: AIS received counter4.ETS.M145B2C48nksrrotbh
dtb_err_v3_loopback1ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter1.ETS.M145B2C29nksrrotbh
dtb_err_v3_loopback2ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter2.ETS.M145B2C30nksrrotbh
dtb_err_v3_loopback3ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter3.ETS.M145B2C31nksrrotbh
dtb_err_v3_loopback4ACCUMULATIONINT8Disturbance counters: Erroneous V3 loopback counter4.ETS.M145B2C32nksrrotbh
dtb_limit1_lowerINTENSITYINTEGERLower limit for disturbance counter 1.ETS.M145B2C6nksrrotbh
dtb_limit1_upperINTENSITYINTEGERUpper limit for disturbance counter 1.ETS.M145B2C7nksrrotbh
dtb_limit2_lowerINTENSITYINTEGERLower limit for disturbance counter 2.ETS.M145B2C8nksrrotbh
dtb_limit2_upperINTENSITYINTEGERUpper limit for disturbance counter 2.ETS.M145B2C9nksrrotbh
dtb_limit3_lowerINTENSITYINTEGERLower limit for disturbance counter 3.ETS.M145B2C10nksrrotbh
dtb_limit3_upperINTENSITYINTEGERUpper limit for disturbance counter 3.ETS.M145B2C11nksrrotbh
dtb_limit4_lowerINTENSITYINTEGERLower limit for disturbance counter 4.ETS.M145B2C12nksrrotbh
dtb_nt1_lost_power1ACCUMULATIONINT8Disturbance counters: NT1 power lost counter1.ETS.M145B2C41nksrrotbh
dtb_nt1_lost_power2ACCUMULATIONINT8Disturbance counters: NT1 power lost counter2.ETS.M145B2C42nksrrotbh
dtb_nt1_lost_power3ACCUMULATIONINT8Disturbance counters: NT1 power lost counter3.ETS.M145B2C43nksrrotbh
dtb_nt1_lost_power4ACCUMULATIONINT8Disturbance counters: NT1 power lost counter4.ETS.M145B2C44nksrrotbh
dtb_nt1_lost_signal1ACCUMULATIONINT8Disturbance counters: NT1 lost signal from ET count1.ETS.M145B2C37nksrrotbh
dtb_nt1_lost_signal2ACCUMULATIONINT8The number of NT1 lost signal or frame alignment disturbances of group 2.ETS.M145B2C38nksrrotbh
dtb_nt1_lost_signal3ACCUMULATIONINT8Disturbance counters: NT1 lost signal from ET count3.ETS.M145B2C39nksrrotbh
dtb_nt1_lost_signal4ACCUMULATIONINT8The number of NT1 lost signal or frame alignment disturbances of group 4.ETS.M145B2C40nksrrotbh
dtb_nt1_lost1ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count1.ETS.M145B2C33nksrrotbh
dtb_nt1_lost2ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count2.ETS.M145B2C34nksrrotbh
dtb_nt1_lost3ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count3.ETS.M145B2C35nksrrotbh
dtb_nt1_lost4ACCUMULATIONINT8Disturbance counters: NT1 lost signal or frame count4.ETS.M145B2C36nksrrotbh
et_dist_error_codeINTENSITYINTEGERError code concerning the short disturbances counters. Zero value means a successful report, nonzero value indicates that no disturbance counters are present. The value is a general DX error code in decimal format.ETS.M145B2C2nksrrotbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_Frame_Alignment

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors. These relate to Frame Alignment counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_frame_alignment_lost1ACCUMULATIONINT8Frame alignment lost counter 1.ETS.M145B2C17nksrrotbh
dtb_frame_alignment_lost2ACCUMULATIONINT8Frame alignment lost counter 2.ETS.M145B2C18nksrrotbh
dtb_frame_alignment_lost3ACCUMULATIONINT8Frame alignment lost counter 3.ETS.M145B2C19nksrrotbh
dtb_frame_alignment_lost4ACCUMULATIONINT8Frame alignment lost counter 4.ETS.M145B2C20nksrrotbh
et_fra_error_codeINTENSITYINTEGERError code concerning the frame alignment error counters. Zero value means a successful report, nonzero value indicates that no frame alignment counters are present. The value is a general DX error code in decimal format.ETS.M145B2C3nksrrotbh
fa_frame_alignment_lost1ACCUMULATIONINT8Frame alignment lost counters: Frame counter 1.ETS.M145B2C56nksrrotbh
fa_frame_alignment_lost2ACCUMULATIONINT8Frame alignment lost counters: Frame counter 2.ETS.M145B2C57nksrrotbh
fa_frame_alignment_lost3ACCUMULATIONINT8Frame alignment lost counters: Frame counter 3.ETS.M145B2C58nksrrotbh
fa_frame_alignment_lost4ACCUMULATIONINT8Frame alignment lost counters: Frame counter 4.ETS.M145B2C59nksrrotbh
fa_limits1_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 1 lower.ETS.M145B2C49nksrrotbh
fa_limits1_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 1 upper.ETS.M145B2C50nksrrotbh
fa_limits2_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 2 lower.ETS.M145B2C51nksrrotbh
fa_limits2_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 2 upper.ETS.M145B2C52nksrrotbh
fa_limits3_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 3 lower.ETS.M145B2C53nksrrotbh
fa_limits3_upperINTENSITYINTEGERFrame alignment lost limits: Stat Limit 3 upper.ETS.M145B2C54nksrrotbh
fa_limits4_lowerINTENSITYINTEGERFrame alignment lost limits: Stat Limit 4 lower.ETS.M145B2C55nksrrotbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_Signal_Missing

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors. These relate to Signal Missing counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
dtb_sig_errors1ACCUMULATIONINT8The number of incoming signal missing disturbances of group 1.ETS.M145B2C13nksrrotbh
dtb_sig_errors2ACCUMULATIONINT8The number of incoming signal missing disturbances of group 2.ETS.M145B2C14nksrrotbh
dtb_sig_errors3ACCUMULATIONINT8The number of incoming signal missing disturbances of group 3.ETS.M145B2C15nksrrotbh
dtb_sig_errors4ACCUMULATIONINT8The number of incoming signal missing disturbances of group 4.ETS.M145B2C16nksrrotbh


Exchange_Terminal.Nokia.GSM.SRR_PCM_Statistics

The disturbances included in the statistics are short disturbances, frame alignment errors, slips, and CRC errors

KPITypeData TypeDescriptionDerivationAdditional Summaries
avail_time_localACCUMULATIONINT8Availability timeETS.M145B2C63nksrrotbh
avail_time_nt1_refACCUMULATIONINT8Availability time NT1 REF PETS.M145B2C79nksrrotbh
avail_time_remoteACCUMULATIONINT8Availability time of the remote endETS.M145B2C71nksrrotbh
avail_time_teACCUMULATIONINT8Availability time TEETS.M145B2C86nksrrotbh
dtb_remote_alarm1ACCUMULATIONINT8Remote end alarm counter 1.ETS.M145B2C25nksrrotbh
dtb_remote_alarm2ACCUMULATIONINT8Remote end alarm counter 2.ETS.M145B2C26nksrrotbh
dtb_remote_alarm3ACCUMULATIONINT8Remote end alarm counter 3.ETS.M145B2C27nksrrotbh
dtb_remote_alarm4ACCUMULATIONINT8Remote end alarm counter 4.ETS.M145B2C28nksrrotbh
error_free_seconds_localACCUMULATIONINT8Error free seconds.ETS.M145B2C67nksrrotbh
error_free_seconds_nt1ACCUMULATIONINT8Error free seconds of NT1.ETS.M145B2C83nksrrotbh
error_free_seconds_remoteACCUMULATIONINT8Error free seconds of the remote end.ETS.M145B2C75nksrrotbh
error_free_seconds_teACCUMULATIONINT8Error free seconds of TE.ETS.M145B2C90nksrrotbh
et_slip_error_codeINTENSITYINTEGERError code concerning the slip counters. Zero value means a successful report, nonzero value indicates that no slip counters are present. The value is a general DX error code in decimal format.ETS.M145B2C4nksrrotbh
et_total_error_codeINTENSITYINTEGERError code concerning the whole report. Zero value means a successful report, nonzero value indicates that no counters are present. The value is a general DX error code in decimal format.ETS.M145B2C1nksrrotbh
slip_negativeACCUMULATIONINT8Counter value for negative slips.ETS.M145B2C60nksrrotbh
slip_positiveACCUMULATIONINT8Counter value for positive slips.ETS.M145B2C61nksrrotbh
unavail_time_localACCUMULATIONINT8Unavailability timeETS.M145B2C64nksrrotbh
unavail_time_nt1_refACCUMULATIONINT8Unavailability time NT1 REF PETS.M145B2C80nksrrotbh
unavail_time_remoteACCUMULATIONINT8Unavailability time of the remote endETS.M145B2C72nksrrotbh
unavail_time_teACCUMULATIONINT8Unavailability time TEETS.M145B2C87nksrrotbh


FQDN Performance Indicators

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


FQDN.Nokia.GSM.FQDN_Clearcodes

FQDN Clearcodes measurements

The performance data measurements for this KPI group are recorded against the combination of FQDN and MSC_Clear_Code (msc_clear_code_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sscc_ringACCUMULATIONINT8The number of clear codes in the ringing phaseFQDNCC.M136B2C4 
sscc_signallingACCUMULATIONINT8The number of clear codes in the signalling phaseFQDNCC.M136B2C3 
sscc_speechACCUMULATIONINT8The number of clear codes in the speech phaseFQDNCC.M136B2C5 


HLR Performance Indicators

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


HLR.Nokia.GSM.Authentication_Count

This table contains information about the AC measurement, which shows the number of the authentication triplets transferred from a specific VLR address.N.B. There is a secondary key of VLR address.

The performance data measurements for this KPI group are recorded against the combination of HLR and VLR_Address (DEST_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
nbr_ansACCUMULATIONINT8The number of answers received in response to the VLR authentication triplet request.ACHDEST.M87B3C4 
nbr_reqACCUMULATIONINT8The number of VLR authentication triplet requests.ACHDEST.M87B3C3 
nbr_triplACCUMULATIONINT8The number of authentication triplets.ACHDEST.M87B3C5 
number_of_quintetsACCUMULATIONINT8The number of transferred authentication quintets.ACHDEST.M87B3C24 
number_of_syncreqACCUMULATIONINT8The number of synchronization requests which can be sent when the mobile rejects the authentication because the sequence number is out of range.ACHDEST.M87B3C22 
number_of_unknownsubscACCUMULATIONINT8The number of unknown subscribers whose data was not found in the ACACHDEST.M87B3C23 


HLR.Nokia.GSM.Authentication_nknss

This table contains information about the AC measurement, which shows the number of authentication triplets transferred from HLR AC to VLR.

KPITypeData TypeDescriptionDerivationAdditional Summaries
missing_data_from_acu0_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 0.ACHHLR.M87B4C0 
missing_data_from_acu1_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 1.ACHHLR.M87B4C1 
missing_data_from_acu10_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 10.ACHHLR.M87B4C10 
missing_data_from_acu11_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 11.ACHHLR.M87B4C11 
missing_data_from_acu12_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 12.ACHHLR.M87B4C12 
missing_data_from_acu13_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 13.ACHHLR.M87B4C13 
missing_data_from_acu14_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 14.ACHHLR.M87B4C14 
missing_data_from_acu15_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 15.ACHHLR.M87B4C15 
missing_data_from_acu2_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 2.ACHHLR.M87B4C2 
missing_data_from_acu3_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 3.ACHHLR.M87B4C3 
missing_data_from_acu4_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 4.ACHHLR.M87B4C4 
missing_data_from_acu5_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 5.ACHHLR.M87B4C5 
missing_data_from_acu6_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 6.ACHHLR.M87B4C6 
missing_data_from_acu7_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 7.ACHHLR.M87B4C7 
missing_data_from_acu8_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 8.ACHHLR.M87B4C8 
missing_data_from_acu9_if_val_is_1INTENSITYINTEGERData is missing from the ACU with identity 9.ACHHLR.M87B4C9 
numberofacusINTENSITYINTEGERNumber of installed ACUs in HLR.ACHHLR.M87B3C25 
numberofanswacusINTENSITYINTEGERNumber of ACUs, which responded to inquiry. This number can be different from the NUMBER OF ACUS in the case when some of the ACUs are temporarily out of order or they are overloaded.ACHHLR.M87B3C26 
restart_in_stu_if_value_is_1INTENSITYINTEGERThis field indicates that duplex restart occurred in STU(s) during the measurement. The counters are unreliable. The field has effect on all report parts. This counter has value 1 in XML report only in case of missing data and it is not sent at all if no restart occurred in STU(s) during the measurement.ACHHLR.M87B3C18 
restartinacuifvalueis_1INTENSITYINTEGERThis field indicates that duplex restart occurred in ACU(s) during the measurement. The counters are unreliable. The field has effect on all report parts. This counter has value 1 in XML report only in case of missing data and it is not sent at all if no restart occurred in ACU(s) during the measurement.The text appears in ASCII report only in case of missing data.ACHHLR.M87B3C27 
tot_nbr_ansACCUMULATIONINT8The total number of returned VLR authentication triplets.ACHHLR.M87B3C7 
tot_nbr_reqACCUMULATIONINT8The total number of VLR authentication triplet requests.ACHHLR.M87B3C6 
tot_nbr_triplACCUMULATIONINT8The total number of authentication triplets.ACHHLR.M87B3C8 
totnumberofquintetsACCUMULATIONINT8The total number of transferred authentication quintets.ACHHLR.M87B3C21 
totnumberofsyncreqACCUMULATIONINT8The total number of synchronization requests which can be sent when the mobile rejects the authentication because the sequence number is out of rangeACHHLR.M87B3C19 
totnumberofunksubsACCUMULATIONINT8The total number of unknown subscribers whose data was not found in the AC.ACHHLR.M87B3C20 
used_space_ac_dbINTENSITYINTEGERThe space used in AC database given as the average number of ACU units in use.ACHHLR.M87B2C1 


HLR.Nokia.GSM.EIR

This measurement contains information about the EIR measurement, which shows the number of mobile stations (MS) on different lists and the number of requests made regarding each listed MS.

KPITypeData TypeDescriptionDerivationAdditional Summaries
overflow_requestsACCUMULATIONINT8The number of device requests in case of overflow. This field is displayed only if, during the measurement, requests of more than 200 devices have been made.EIRH.M85B3C11 
regtypeisglobal_if_value_is_1INTENSITYINTEGER(Obsolete, EIRI counters now supported under EIR_IMEI object) The allowed value for this counter is 1. If counter is sent in XML report with respective value, it means that the registration type of device is GLOBAL.obsolete.obsolete 
regtypeislocal_if_value_is_1INTENSITYINTEGER(Obsolete, EIRI counters now supported under EIR_IMEI object) The allowed value for this counter is 1. If counter is sent in XML report with respective value, it means that the registration type of device is LOCAL.obsolete.obsolete 
req_for_duplicated_eqACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is (POSSIBLY) DUPLICATED - this IMEI (possibly) has been copied into several different mobiles If IMEI belongs to black list then the reason code is DUPLICATED If IMEI belongs to grey list then the reason code is POSSIBLY DUPLICATEDobsolete.obsolete 
req_for_impersonated_eqACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is (POSSIBLY) IMPERSONATED - this IMEI is (possibly) not corresponding to the white list, it is (possibly) illegally issued and not provided by the manufacturer, operator, or a type of approval house. If IMEI belongs to black list then the reason code is IMPERSONATED If IMEI belongs to grey list then the reason code is POSSIBLY IMPERSONATEDobsolete.obsolete 
req_for_other_reasonACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is some otherobsolete.obsolete 
req_for_pos_illegal_eqACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is (POSSIBLY) ILLEGAL - the device is (possibly) illegal. If IMEI belongs to black list then the reason code is ILLEGAL If IMEI belongs to grey list then reason code is POSSIBLY ILLEGALobsolete.obsolete 
req_for_pos_not_prop_work_eqACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is (POSSIBLY) NOT WORKING - the device is (possibly) out of order. If IMEI belongs to black list then the reason code is NOT WORKING. If IMEI belongs to grey list then the reason code is POSSIBLY NOT WORKINGobsolete.obsolete 
req_for_stolen_eqACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is STOLEN - the device is stolen. If the reason code is STOLEN, IMEI always belongs to black list.obsolete.obsolete 
requestsACCUMULATIONINT8(Obsolete, EIRI counters now supported under EIR_IMEI object) The number of IMEI requests for those devices whose reason code is NEW - new device. If the reason code is NEW, the IMEI always belongs to grey list.obsolete.obsolete 
tot_black_entriesINTENSITYINTEGERThe total number of individual devices and series of devices on the black list.EIRH.M85B3C1 
tot_black_reqACCUMULATIONINT8The total number of IMEI requests received concerning devices on the black list during the measurement.EIRH.M85B3C7 
tot_grey_entriesINTENSITYINTEGERThe total number of individual devices and series of devices on the grey list.EIRH.M85B3C8 
tot_grey_reqACCUMULATIONINT8The total number of IMEI requests received concerning devices on the grey list during the measurement.EIRH.M85B3C12 
tot_unknown_reqINTENSITYINTEGERThe total number of individual devices and series of devices on the white list.EIRH.M85B3C10 
tot_white_reqACCUMULATIONINT8The total number of IMEI requests received concerning devices on the white list during the measurement.EIRH.M85B3C9 
used_space_blackINTENSITYFLOATThe amount of space used on the BLACK LIST as a percentage.EIRH.M85B2C1 
used_space_greyINTENSITYFLOATThe amount of space used on the GREY LIST as a percentage.EIRH.M85B2C2 
used_space_whiteINTENSITYFLOATThe amount of space used on the WHITE LIST as a percentage.EIRH.M85B2C3 


HLR.Nokia.GSM.GPRS_Subscribers

This section describes the counters of M352: MeO HLR / DEST. N.B. There is a secondary key of SGSN ISDN Address

The performance data measurements for this KPI group are recorded against the combination of HLR and SGSN_address (sgsn_address_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
average_nbr_of_subscribers_sgsnINTENSITYFLOATFor the calculation of the average number of home subscribers for each SGSN, including SGSNs outside the home network, the number of subscribers is fetched from the HLR for each SGSN at five-minute. Note: one subscriber can appear on the VLR and SGSN list at the same time if it is both GPRS- and GSM-attached.VLRMS.M352B9C3 
current_nbr_of_subscribers_sgsnINTENSITYINTEGERNumber of home subscribers for each SGSN, including SGSNs outside the home network at the reporting moment. Note: one subscriber can appear on the VLR and SGSN list at the same time if it is both GPRS- and GSM-attached.VLRMS.M352B9C2 
sgsn_unreliableINTENSITYINTEGERThis counter can appear in the XML report with value 1 when the Average Number of GPRS Subscribers counter is unreliable (there were a SGSN address cleaning in the HLR database during the measurement which causes a special problem in the procedure of the gathering average counters, however this is a rare situation)VLRMS.M352B11C1 


HLR.Nokia.GSM.HLR_Signalling_Point_Traffic_User

Signalling traffic measurements

The performance data measurements for this KPI group are recorded against the combination of HLR, SIO (sio_id) and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8The number of SIF and SIO received with the given SIO.UTRAHLR.M214B2C1 
sif_sio_transACCUMULATIONINT8The number of SIF and SIO transmitted with the given SIO.UTRAHLR.M214B2C2 


HLR.Nokia.GSM.HLRU_Data

This section describes the counters of M79

KPITypeData TypeDescriptionDerivationAdditional Summaries
hlr_genhlrss_numberofanswhlrusINTENSITYINTEGERNumber of HLRUs which responded to inquiry. This number can be different from the NUMBEROF HLRUS in the case when some of the HLRUs are temporarily out of order or they are overloaded. The field has effect on the rest of the reportHLRSS.M79B1C14 
hlr_genhlrss_numberofhlrusINTENSITYINTEGERTotal number of HLRU pairs in HLR.HLRSS.M79B1C13 
missing_data_from_hlr0_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 0 has missing data.)HLRSS.M79B13C0 
missing_data_from_hlr1_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 1 has missing data.)HLRSS.M79B13C1 
missing_data_from_hlr10_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 10 has missing data.)HLRSS.M79B13C10 
missing_data_from_hlr11_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 11 has missing data.)HLRSS.M79B13C11 
missing_data_from_hlr12_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 12 has missing data.)HLRSS.M79B13C12 
missing_data_from_hlr13_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 13 has missing data.)HLRSS.M79B13C13 
missing_data_from_hlr14_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 14 has missing data.)HLRSS.M79B13C14 
missing_data_from_hlr15_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 15 has missing data.)HLRSS.M79B13C15 
missing_data_from_hlr2_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 2 has missing data.)HLRSS.M79B13C2 
missing_data_from_hlr3_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 3 has missing data.)HLRSS.M79B13C3 
missing_data_from_hlr4_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 4 has missing data.)HLRSS.M79B13C4 
missing_data_from_hlr5_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 5 has missing data.)HLRSS.M79B13C5 
missing_data_from_hlr6_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 6 has missing data.)HLRSS.M79B13C6 
missing_data_from_hlr7_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 7 has missing data.)HLRSS.M79B13C7 
missing_data_from_hlr8_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 8 has missing data.)HLRSS.M79B13C8 
missing_data_from_hlr9_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 9 has missing data.)HLRSS.M79B13C9 
restart_in_hlru_if_value_is_1INTENSITYINTEGERThis field indicates that duplex restart occurred in HLRU(s) during the measurement. The counters are unreliable. The field has effect on all report parts.HLRSS.M79B12C1 
restart_in_stu_if_value_is_1INTENSITYINTEGERThis field indicates that duplex restart occurred in STU(s) during the measurement. The counters are unreliable. The field has effect on all report part.HLRSS.M79B12C2 


HLR.Nokia.GSM.Mobility_Basic_Services

Stores the counters related to basic services. N.B. There is a secondary key of basic_service

The performance data measurements for this KPI group are recorded against the combination of HLR and Basic_Service (basic_service_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_SRI_SUCC_MEMPERCENTAGEFLOATPercentage of successfully answered SRIs for a specific basic service in the HLR during the measurement period, where the called number was a member of hunting ringing group.percentok({SRI_SUCC_MEM}, {SRI_ATTEMPT_MEM})nkhlrsubbh
attempt_sriACCUMULATIONINT8The number of SRI attempts for the basic service. H1BS.M83B10C4nkhlrsubbh
basic_serv_countACCUMULATIONINT8The number of activated basic services.H1BS.M83B10C2nkhlrsubbh
hlr_sri_par_rgn_forwACCUMULATIONINT8Number of forwarded SRIs for a specific basic service in the HLR during the measurement period where the called number was a parallel ringing group number. This counter appears only if the parallel alerting feature is available and active.H1BS.M83B10C13nkhlrsubbh
hlr_sri_par_rgn_succACCUMULATIONINT8Number of successfully answered SRIs for a specific basic service in the HLR during the measurement period where the called number was a parallel ringing group number. This counter appears only if the parallel alerting feature is available and active.H1BS.M83B10C12nkhlrsubbh
hlr_sri_par_rgnACCUMULATIONINT8Number of received SRIs for a specific basic service in the HLR during the measurement period where the called number was a parallel ringing group number. This counter is updated when the user exists in the database and the basic service is provisioned. This counter appears only if the parallel alerting feature is available and active.H1BS.M83B10C11nkhlrsubbh
hlr_sri_rgn_succACCUMULATIONINT8Number of successfully answered SRI for a specific basic service in the HLR when Ringing Group Number (RGN) is called during the measurement period.H1BS.M83B10C7nkhlrsubbh
hlr_sri_rgnACCUMULATIONINT8Number of received SRI for a specific basic service in the HLR when Ringing Group Number (RGN) is called during the measurement period. This counter is updated when the user exists in the database and the basic service is provisioned.H1BS.M83B10C6nkhlrsubbh
hlr_sri_seq_par_rgn_forwACCUMULATIONINT8Number of forwarded SRIs for a specific basic service in the HLR during the measurement period where the called number was a sequential/parallel ringing group number. This counter appears only if the sequential and parallel alerting features are available and active.H1BS.M83B10C16nkhlrsubbh
hlr_sri_seq_par_rgn_succACCUMULATIONINT8Number of successfully answered SRIs for a specific basic service in the HLR during the measurement period where the called number was a sequential/parallel ringing group number. This counter appears only if the sequential and parallel alerting features are available and active.H1BS.M83B10C15nkhlrsubbh
hlr_sri_seq_par_rgnACCUMULATIONINT8Number of received SRIs for a specific basic service in the HLR during the measurement period where the called number was a sequential/parallel ringing group number. This counter is updated when the user exists in the database and the basic service is provisioned. This counter appears only if the sequential and parallel alerting features are available and active.H1BS.M83B10C14nkhlrsubbh
hlr_sri_seq_rgn_forwACCUMULATIONINT8Number of forwarded SRIs for a specific basic service in the HLR during the measurement period where the called number was a sequential ringing group number. This counter appears only if the sequential alerting feature is available and active.H1BS.M83B10C10nkhlrsubbh
hlr_sri_seq_rgn_succACCUMULATIONINT8Number of successfully answered SRIs for a specific basic service in the HLR during the measurement period where the called number was a sequential ringing group number. This counter appears only if the sequential alerting feature is available and active.H1BS.M83B10C9nkhlrsubbh
hlr_sri_seq_rgnACCUMULATIONINT8Number of received SRIs for a specific basic service in the HLR during the measurement period where the called number was a sequential ringing group number. This counter is updated when the user exists in the database and the basic service is provisioned. This counter appears only if the sequential alerting feature is available and active.H1BS.M83B10C8nkhlrsubbh
hlr_sri_withbor_attemptACCUMULATIONINT8Number of received SRIs for a specific basic service in the HLR with Basic Optimal Routing indication (during the measurement period).H1BS.M83B10C17nkhlrsubbh
hlr_sri_withbor_succACCUMULATIONINT8Number of successfully answered SRIs for a specific basic service in the HLR with Basic Optimal Routing indication (during the measurement period).H1BS.M83B10C18nkhlrsubbh
SRI_ATTEMPT_MEMACCUMULATIONINT8Number of received SRIs for a specific basic service in the HLR during the measurement period, where the called number was a member of hunting ringing group.H1BS.M83B10C19nkhlrsubbh
SRI_INTELLIG_RING_GRP_NUM_SUCCACCUMULATIONINT8Number of successfully answered SRIs for a specific basic service in the HLR during the measurement period, where the called number was an intelligent hunting ringing group number.H1BS.M83B10C22nkhlrsubbh
SRI_INTELLIG_RING_GRP_NUMB_FWDACCUMULATIONINT8Number of forwarded SRIs for a specific basic service in the HLR during the measurement period, where the called number was an intelligent hunting ringing group number.H1BS.M83B10C23nkhlrsubbh
SRI_INTELLIG_RING_GRP_NUMACCUMULATIONINT8Number of received SRIs for a specific basic service in the HLR during the measurement period, where the called number was an intelligent hunting ringing group number.H1BS.M83B10C21nkhlrsubbh
SRI_SUCC_MEMACCUMULATIONINT8Number of successfully answered SRIs for a specific basic service in the HLR during the measurement period, where the called number was a member of hunting ringing group.H1BS.M83B10C20nkhlrsubbh
succ_sriACCUMULATIONINT8The number of successful SRIs for the basic service. H1BS.M83B10C5nkhlrsubbh


HLR.Nokia.GSM.Mobility

This measurement contains the measurement results from the HLR measurements.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ATI_MULTISIM_GROUP_ATTEMPTACCUMULATIONINT8Total number of ATI (Any Time Interrogation) attempts for MultiSIM group.HL1HLR.M83B9C1nkhlrsubbh
ATI_MULTISIM_GROUP_SUCCACCUMULATIONINT8Total number of ATI (Any Time Interrogation) successful attempts for MultiSIM group.HL1HLR.M83B9C2nkhlrsubbh
camel_subscINTENSITYINTEGERThe number of subscribers that have at least one CAMEL subscription active. HL1HLR.M83B11C2nkhlrsubbh
GPRS_GROUP_MEMBERS_ATTEMPTACCUMULATIONINT8Number of requested Location Registrations by MultiSIM member subscribers sent by SGSNs during the measurement period.HL1HLR.M83B5C11nkhlrsubbh
GPRS_GROUP_MEMBERS_SUCCACCUMULATIONINT8Number of successful Location Registrations by MultiSIM member subscribers sent by SGSNs during the measurement period.HL1HLR.M83B5C12nkhlrsubbh
hlr_calldivertintattemptACCUMULATIONINT8Number of call divert interrogation attempts for ringing group. This counter appears only if the parallel alerting feature is available and active.HL1HLR.M83B11C13nkhlrsubbh
hlr_calldivertintsuccessfulACCUMULATIONINT8Number of successful call divert interrogations for ringing group. This counter appears only if the parallel alerting feature is available and active.HL1HLR.M83B11C14nkhlrsubbh
hlr_callhandlingACCUMULATIONINT8Database transaction related to incoming call handling, such as fetching and updating the subscriber data. In mobile-terminating call, the counter is increased by one.HL1HLR.M83B6C1nkhlrsubbh
hlr_lcs_subscribercountINTENSITYINTEGERNumber of subscribers that have at least one location service class provisioned.HL1HLR.M83B11C1nkhlrsubbh
hlr_missingdata_hlru0_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 0 has missing data.)HL1HLR.M83B13C0nkhlrsubbh
hlr_missingdata_hlru1_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 15 has missing data.)HL1HLR.M83B13C15nkhlrsubbh
hlr_missingdata_hlru10_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 1 has missing data.)HL1HLR.M83B13C1nkhlrsubbh
hlr_missingdata_hlru11_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 10 has missing data.)HL1HLR.M83B13C10nkhlrsubbh
hlr_missingdata_hlru12_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 11 has missing data.)HL1HLR.M83B13C11nkhlrsubbh
hlr_missingdata_hlru13_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 12 has missing data.)HL1HLR.M83B13C12nkhlrsubbh
hlr_missingdata_hlru14_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 13 has missing data.)HL1HLR.M83B13C13nkhlrsubbh
hlr_missingdata_hlru15_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 14 has missing data.)HL1HLR.M83B13C14nkhlrsubbh
hlr_missingdata_hlru2_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 2 has missing data.)HL1HLR.M83B13C2nkhlrsubbh
hlr_missingdata_hlru3_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 3 has missing data.)HL1HLR.M83B13C3nkhlrsubbh
hlr_missingdata_hlru4_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 4 has missing data.)HL1HLR.M83B13C4nkhlrsubbh
hlr_missingdata_hlru5_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 5 has missing data.)HL1HLR.M83B13C5nkhlrsubbh
hlr_missingdata_hlru6_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 6 has missing data.)HL1HLR.M83B13C6nkhlrsubbh
hlr_missingdata_hlru7_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 7 has missing data.)HL1HLR.M83B13C7nkhlrsubbh
hlr_missingdata_hlru8_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 8 has missing data.)HL1HLR.M83B13C8nkhlrsubbh
hlr_missingdata_hlru9_valueis1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 9 has missing data.)HL1HLR.M83B13C9nkhlrsubbh
hlr_mobility_managementACCUMULATIONINT8Database transactions related to subscriber mobility. In a subscriber location update the counter is increased by one.HL1HLR.M83B6C2nkhlrsubbh
hlr_normal_gprs_luattemptACCUMULATIONINT8Number of requested Location Registrations (UpdateLocationForGPRS MAP operation) sent by SGSNs during the measurement period. These events are not included in the former normal LU counters. Only those location registrations are shown here which can be seen in the HLR. (Inter SGSN routing area updates)HL1HLR.M83B5C9nkhlrsubbh
hlr_normal_gprs_lusuccACCUMULATIONINT8Number of successful Location Registration (UpdateLocationForGPRS_ACK MAP operation) responses sent to SGSNs during the measurement period. These events are not included in the former normal LU counters. Only those location registrations are shown here which can be seen in the HLR. (Inter SGSN routing area updates)HL1HLR.M83B5C10nkhlrsubbh
hlr_primarymemberintattemptACCUMULATIONINT8Number of primary member interrogation attempts for ringing group. This counter appears only if the parallel alerting feature is available and active.HL1HLR.M83B11C11nkhlrsubbh
hlr_primarymemberintsuccACCUMULATIONINT8Number of successful primary member interrogations for ringing group. This counter appears only if the parallel alerting feature is available and active.HL1HLR.M83B11C12nkhlrsubbh
hlr_restartinhlruifvalueis1ACCUMULATIONINT8This field indicates that duplex restart occurred in HLRU(s) during the measurement. The counters are unreliable. The field has effect on all report parts.HL1HLR.M83B12C1nkhlrsubbh
hlr_restartinstuifvalueis1ACCUMULATIONINT8This field indicates that duplex restart occurred in STU(s) during the measurement. The counters are unreliable. The field has effect on all report part.HL1HLR.M83B12C2nkhlrsubbh
hlr_unknown_sri_attemptACCUMULATIONINT8Number of SRI attempts when there is no provisioned basic service for the MSISDN (received in SRI) or the database reading has failed (in these cases the Basic Service code is not known). These are always unsuccessful SRI operations. (Note: this counter does not covers those SRI attempts when the subscriber is unknown in the HLR database)HL1HLR.M83B11C4nkhlrsubbh
hlru_in_hlrINTENSITYINTEGERThe number of HLRU units in the HLR.HL1HLR.M83B1C13nkhlrsubbh
hlru_sentINTENSITYINTEGERThe number of HLRU units that have sent data.HL1HLR.M83B1C14nkhlrsubbh
HOME_SUBS_GROUP_MEMBERS_FAILACCUMULATIONINT8Total number of failed location updates by Ringing group members during the measurement period.HL1HLR.M83B5C8nkhlrsubbh
HOME_SUBS_GROUP_MEMBERS_SUCCACCUMULATIONINT8Total number of successful location updates by Ringing group members during the measurement period.HL1HLR.M83B5C7nkhlrsubbh
occbs_countACCUMULATIONINT8OCCBS count.HL1HLR.M83B7C1nkhlrsubbh
occbs_mml_passivationsACCUMULATIONINT8OCCBS MML deactivated.HL1HLR.M83B7C5nkhlrsubbh
occbs_recallACCUMULATIONINT8OCCBS recall.HL1HLR.M83B7C7nkhlrsubbh
occbs_system_passivationsACCUMULATIONINT8OCCBS system deactivated.HL1HLR.M83B7C6nkhlrsubbh
occbs_user_activationsACCUMULATIONINT8OCCBS user activated.HL1HLR.M83B7C2nkhlrsubbh
occbs_user_inquiryACCUMULATIONINT8OCCBS user inquiry.HL1HLR.M83B7C8nkhlrsubbh
occbs_user_passivationsACCUMULATIONINT8OCCBS user deactivated.HL1HLR.M83B7C4nkhlrsubbh
PSI_MULTISIM_GROUP_ATTEMPTACCUMULATIONINT8Total number of PSI (Provide Subscriber Information) successful attempts for MultiSIM group.HL1HLR.M83B9C3nkhlrsubbh
PSI_MULTISIM_GROUP_SUCCACCUMULATIONINT8Total number of PSI (Provide Subscriber Information) attempts for MultiSIM group.HL1HLR.M83B9C4nkhlrsubbh
req_hunting_order_inquir_succACCUMULATIONINT8Number of successful hunting order inquiries for ringing group. This counter appears only if the sequential alerting feature is available and active.HL1HLR.M83B11C8nkhlrsubbh
req_hunting_order_inquirACCUMULATIONINT8Number of hunting order inquiry attempts for ringing group. This counter appears only if the sequential alerting feature is available and active.HL1HLR.M83B11C7nkhlrsubbh
req_hunting_order_modif_succACCUMULATIONINT8Number of successful hunting order modifications for ringing group. This counter appears only if the sequential alerting feature is available and active.HL1HLR.M83B11C6nkhlrsubbh
req_hunting_order_modifACCUMULATIONINT8Number of hunting order modification attempts for ringing group. This counter appears only if the sequential alerting feature is available and active.HL1HLR.M83B11C5nkhlrsubbh
srismscfuattemptACCUMULATIONINT8Number of received SRI_for_SM for unconditional SMS forwarding in the HLR during the measurement period. This counter is updated when the user exists in the database and the SMS forwarding is active. In this case, the T21 basic service (MT SM) is not updated.HL1HLR.M83B11C9nkhlrsubbh
srismscfusuccessfulACCUMULATIONINT8Number of successfully answered SRI_for_SMs for unconditional SMS forwarding in the HLR during the measurement period. In this case, the T21 basic service (MT SM) is not updated. The successful SRI SMS-CFU update does not mean a successful SMS Forwarding event, because if the forwarded to number does not belong to the allowed (co-operation) PLMNs, then the forwarding is overridden. In this case the SMS is delivered to the forwarding subscriber (a normal SRI_for_SM procedure is executed).HL1HLR.M83B11C10nkhlrsubbh
subs_gprsINTENSITYINTEGERNumber of GPRS subscribers.HL1HLR.M83B8C1nkhlrsubbh
succ_home_retACCUMULATIONINT8The number of successful home subscriber returns from other PLMNs.HL1HLR.M83B5C3nkhlrsubbh
succ_home_visitsACCUMULATIONINT8The number of successful home subscriber visits to other PLMNs.HL1HLR.M83B5C1nkhlrsubbh
SYNCHRONIZED_TO_GROUP_FAILEDACCUMULATIONINT8Total number of failed synchronization of supplementary services for MultiSIM group.HL1HLR.M83B9C6nkhlrsubbh
SYNCHRONIZED_TO_GROUP_SUCCACCUMULATIONINT8Total number of successful synchronization attempts of supplementary services for MultiSIM group.HL1HLR.M83B9C5nkhlrsubbh
tccbs_countACCUMULATIONINT8TCCBS count.HL1HLR.M83B7C9nkhlrsubbh
tccbs_mml_passivationsACCUMULATIONINT8TCCBS MML deactivated.HL1HLR.M83B7C13nkhlrsubbh
tccbs_recallACCUMULATIONINT8TCCBS recall.HL1HLR.M83B7C15nkhlrsubbh
tccbs_system_activationsACCUMULATIONINT8TCCBS system activated.HL1HLR.M83B7C11nkhlrsubbh
tccbs_system_passivationsACCUMULATIONINT8TCCBS system deactivated.HL1HLR.M83B7C14nkhlrsubbh
tot_fail_home_luACCUMULATIONINT8The total number of failed update attempts on the home subscriber location.HL1HLR.M83B5C6nkhlrsubbh
tot_succ_home_luACCUMULATIONINT8The total number of successful updates on the home subscriber location.HL1HLR.M83B5C5nkhlrsubbh
used_sp_in_hlrdbINTENSITYFLOATThe space used in HLR database.HL1HLR.M83B2C1nkhlrsubbh


HLR.Nokia.GSM.Rejected_Calls

This section describes the counters of M114

KPITypeData TypeDescriptionDerivationAdditional Summaries
rej_error_foundINTENSITYINTEGERTag appears at the end of the given counter group with field value 244 if an unexpected error situation has occurred.REJHLR.M114B2C13nkhlrsubbh
rej_exchg_inc_percentx10INTENSITYFLOATThe ticket service rejection percentage (0.0...100.0) of all the signalling units of the exchange regardless of the computer units that have been under observation.REJHLR.M114B2C7nkhlrsubbh
rej_exchg_incACCUMULATIONINT8The total sum of rejected incoming service requests (0...999999999) at the ticket service of all the signaling units of the exchange regardless of the computer units that have been under observation.REJHLR.M114B2C6nkhlrsubbh
rej_exchg_outgoingACCUMULATIONINT8The number of rejected service requests (0...999999999) that have exceeded the higher rejection limit of the message buffer on the outgoing side. The number of rejected service requests that have exceeded the higher rejection limit of the CPU load on the incoming side.REJHLR.M114B2C8nkhlrsubbh
rej_no_resp_from_lrmproINTENSITYINTEGERTag appears at the end of the given counter group with field value 242 if the signaling unit has not sent the required information for the following exchange-related counters: REJ_EXCHG_INC, REJ_EXCHG_INC_PERCENT*10, REJ_EXCHG_OUTGOING.REJHLR.M114B2C10nkhlrsubbh
rej_no_resp_from_signprbINTENSITYINTEGERTag appears at the end of the given counter group with field value 243 if the required information has not been received from the signalling process family that provides counters of the measured object.REJHLR.M114B2C11nkhlrsubbh
rej_observ_restartedINTENSITYINTEGERTag appears at the end of the given counter group with field value 16 if the signalling unit has not responded during the previous results accumulation period. Therefore, the observation has been restarted during the current results accumulation period. The counters is printed out during the following period.REJHLR.M114B2C12nkhlrsubbh
rej_report_inquiry_failINTENSITYINTEGERTag appears at the end of the given counter group with field value 241 if only part of the required information is received from the signalling process family that provides the counters of the measured object.REJHLR.M114B2C9nkhlrsubbh


HLR.Nokia.GSM.SCCP_Single_Meter

This table contains measurement data of one or more signalling networks.

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_hop_counterACCUMULATIONINT8Hop counter violationSINHLR.M219B2C16nkhlrsubbh
rea_err_failACCUMULATIONINT8Reassembly error - Reassembly failedSINHLR.M219B2C13nkhlrsubbh
rea_err_segmentACCUMULATIONINT8Reassembly error - Segment received out of sequenceSINHLR.M219B2C11nkhlrsubbh
rea_err_spaceACCUMULATIONINT8Reassembly error - No reassembly spaceSINHLR.M219B2C12nkhlrsubbh
rea_err_timer_expiryACCUMULATIONINT8Reassembly error - Timer T(reass) expirySINHLR.M219B2C10nkhlrsubbh
sccp_from_localACCUMULATIONINT8Processed SCCP messages from a local subsystem.SINHLR.M219B2C2nkhlrsubbh
sccp_to_localACCUMULATIONINT8Processed SCCP messages to a local subsystem.SINHLR.M219B2C1nkhlrsubbh
sccp_totalACCUMULATIONINT8Processed SCCP messages, totalSINHLR.M219B2C5nkhlrsubbh
sccp_userACCUMULATIONINT8Processed users independent SCCP messages.SINHLR.M219B2C4nkhlrsubbh
seg_err_failACCUMULATIONINT8Segmentation error - Segmentation failedSINHLR.M219B2C15nkhlrsubbh
seg_err_no_supportACCUMULATIONINT8Segmentation error - Segmenting not SupportedSINHLR.M219B2C14nkhlrsubbh
stp_gtACCUMULATIONINT8STP messages requiring GT translation.SINHLR.M219B2C8nkhlrsubbh
stpACCUMULATIONINT8Processed STP messagesSINHLR.M219B2C3nkhlrsubbh
with_gt_from_localACCUMULATIONINT8Messages requiring GT translation from a local subsystem.SINHLR.M219B2C7nkhlrsubbh
with_gt_to_localACCUMULATIONINT8Messages requiring GT translation to a local subsystem.SINHLR.M219B2C6nkhlrsubbh
with_gt_totalACCUMULATIONINT8Messages requiring GT translation, totalSINHLR.M219B2C9nkhlrsubbh


HLR.Nokia.GSM.SCCP_Subsystem_Local_Availability

This measurement contains measurement data of one or more signalling networks.N.B. There is a secondary key of signalling network

The performance data measurements for this KPI group are recorded against the combination of HLR and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
dura_of_local_sccp_unavailableACCUMULATIONINT8Duration of the unavailability of a local SCCPLOCHLR.M218B2C5nkhlrsubbh
duration_sccpACCUMULATIONINT8Duration of the unavailability of a local SCCPsubstr(LOCHLR.M218B2C5, 2, 0) * 86400 + substr(LOCHLR.M218B2C5, 2, 2) * 3600 + substr(LOCHLR.M218B2C5, 2, 4) * 60 + substr(LOCHLR.M218B2C5, 2, 6)nkhlrsubbh
start_time_sccp_busyINTENSITYINTEGERStart of unavailability of a local SCCP due to maintenance busyLOCHLR.M218B2C2nkhlrsubbh
start_time_sccp_congINTENSITYINTEGERStart of unavailability of a local SCCP due to congestionLOCHLR.M218B2C3nkhlrsubbh
start_time_sccp_failINTENSITYINTEGERStart of unavailability of a local SCCP due to failureLOCHLR.M218B2C1nkhlrsubbh
stop_time_sccpINTENSITYINTEGERStop of unavailability of a local SCCPLOCHLR.M218B2C4nkhlrsubbh


HLR.Nokia.GSM.SCCP_Subsystem

This measurement contains measurement data of one or more SCCP subsystems.N.B. There is a secondary key of signalling_network and also of subsystem.

The performance data measurements for this KPI group are recorded against the combination of HLR, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
csm_accepted_localACCUMULATIONINT8Acceptance of a coordinated state modification request by a local subsystemSUBHLR.M217B2C1nkhlrsubbh
csm_accepted_remoteACCUMULATIONINT8Acceptance of a coordinated state modification request by a remote subsystemSUBHLR.M217B2C2nkhlrsubbh
csm_rejected_localACCUMULATIONINT8Rejection of a coordinated state modification request by a local subsystemSUBHLR.M217B2C3nkhlrsubbh
csm_rejected_remoteACCUMULATIONINT8Rejection of a coordinated state modification request by a remote subsystemSUBHLR.M217B2C4nkhlrsubbh
dt1_receivedACCUMULATIONINT8DT 1 messages received from MTP per sink SSNSUBHLR.M217B2C15nkhlrsubbh
dt1_transACCUMULATIONINT8DT 1 messages sent to MTP per source SSNSUBHLR.M217B2C16nkhlrsubbh
dt2_receivedACCUMULATIONINT8DT 2 messages received from MTP per sink SSNSUBHLR.M217B2C17nkhlrsubbh
dt2_transACCUMULATIONINT8DT 2 messages sent to MTP per source SSNSUBHLR.M217B2C18nkhlrsubbh
ed_receivedACCUMULATIONINT8ED messages received from MTP per sink SSNSUBHLR.M217B2C19nkhlrsubbh
ed_transACCUMULATIONINT8ED messages sent to MTP per source SSNSUBHLR.M217B2C20nkhlrsubbh
err_segmentationACCUMULATIONINT8Messages too large for segmentationSUBHLR.M217B2C23nkhlrsubbh
msg_all_localACCUMULATIONINT8All messages related to a local subsystemSUBHLR.M217B2C9nkhlrsubbh
msg_from_local_with_gtACCUMULATIONINT8Messages addressed from a local subsystem that require GT translationSUBHLR.M217B2C8nkhlrsubbh
msg_from_local_without_gtACCUMULATIONINT8Messages addressed from a local subsystem that do not require GT translationSUBHLR.M217B2C7nkhlrsubbh
msg_received_class0ACCUMULATIONINT8All received messages in protocol class 0SUBHLR.M217B2C13nkhlrsubbh
msg_received_class1ACCUMULATIONINT8All received messages in protocol class 1SUBHLR.M217B2C14nkhlrsubbh
msg_redundantACCUMULATIONINT8All messages transmitted to the redundant subsystemSUBHLR.M217B2C10nkhlrsubbh
msg_to_local_with_gtACCUMULATIONINT8Messages addressed to a local subsystem that require GT translationSUBHLR.M217B2C6nkhlrsubbh
msg_to_local_without_gtACCUMULATIONINT8Messages addressed to a local subsystem that do not require GT translationSUBHLR.M217B2C5nkhlrsubbh
msg_trans_class0ACCUMULATIONINT8All transmitted messages in protocol class 0SUBHLR.M217B2C11nkhlrsubbh
msg_trans_class1ACCUMULATIONINT8All transmitted messages in protocol class 1SUBHLR.M217B2C12nkhlrsubbh
prohibited_start_timeACCUMULATIONINT8Start of local subsystem prohibitedSUBHLR.M217B2C21nkhlrsubbh
prohibited_stop_timeACCUMULATIONINT8Stop of local subsystem prohibitedSUBHLR.M217B2C22nkhlrsubbh


HLR.Nokia.GSM.Security_Report

This measurement contains the results of the security counter measurement. The measurement collects information about the system from the security point of view.N.B. There is a secondary key of security_counter

The performance data measurements for this KPI group are recorded against the combination of HLR and Security_Counter (security_counter_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
critical_limitACCUMULATIONINT8Critical limit is not set for successful events. The operator cannot set a critical limit for this counter.LSEC.M176B17C2nkhlrsubbh
lo_term_count_reset_ddINTENSITYINTEGERCounter gives the day of long term counters reset time.LSEC.M176B0C4nkhlrsubbh
lo_term_count_reset_hourINTENSITYINTEGERCounter gives the hours of long term counters reset time.LSEC.M176B0C5nkhlrsubbh
lo_term_count_reset_minINTENSITYINTEGERCounter gives the minutes of long term counters reset time.LSEC.M176B0C6nkhlrsubbh
lo_term_count_reset_mmINTENSITYINTEGERCounter gives the month of long term counters reset time.LSEC.M176B0C3nkhlrsubbh
lo_term_count_reset_secINTENSITYINTEGERCounter gives the seconds of long term counters reset time.LSEC.M176B0C7nkhlrsubbh
lo_term_count_reset_yyINTENSITYINTEGERCounter gives the year of long term counters reset time.LSEC.M176B0C2nkhlrsubbh
long_term_totalACCUMULATIONINT8This counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B17C3nkhlrsubbh
reason_for_reportINTENSITYINTEGERCounter gives a value which tells the reason for report. 1 = PERIODICAL, 2 = OUTPUT TIME CHANGED, 3 = CRITICAL LIMIT, 4 = OPERATORLSEC.M176B0C1nkhlrsubbh
sec_critical_limit_10INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B10C2nkhlrsubbh
sec_critical_limit_11INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B11C2nkhlrsubbh
sec_critical_limit_12INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B12C2nkhlrsubbh
sec_critical_limit_13INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B13C2nkhlrsubbh
sec_critical_limit_14INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B14C2nkhlrsubbh
sec_critical_limit_15INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B15C2nkhlrsubbh
sec_critical_limit_16INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B16C2nkhlrsubbh
sec_critical_limit_1INTENSITYINT8Critical limit is not set for successful events. The operator cannot set a critical limit for this counter.LSEC.M176B1C2nkhlrsubbh
sec_critical_limit_2INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B2C2nkhlrsubbh
sec_critical_limit_3INTENSITYINT8Critical limit is not set for successful events. The operator cannot set a critical limit for this counter.LSEC.M176B3C2nkhlrsubbh
sec_critical_limit_4INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B4C2nkhlrsubbh
sec_critical_limit_5INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B5C2nkhlrsubbh
sec_critical_limit_6INTENSITYINT8Critical limit is not set for successful events. The operator cannot set a critical limit for this counter.LSEC.M176B6C2nkhlrsubbh
sec_critical_limit_7INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B7C2nkhlrsubbh
sec_critical_limit_8INTENSITYINT8Counter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.LSEC.M176B8C2nkhlrsubbh
sec_critical_limit_9INTENSITYINT8Critical limit is not set for creating new users. The operator cannot set a critical limit for this counter.LSEC.M176B9C2nkhlrsubbh
sec_long_term_total_10ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B10C3nkhlrsubbh
sec_long_term_total_11ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B11C3nkhlrsubbh
sec_long_term_total_12ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B12C3nkhlrsubbh
sec_long_term_total_13ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B13C3nkhlrsubbh
sec_long_term_total_14ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B14C3nkhlrsubbh
sec_long_term_total_15ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B15C3nkhlrsubbh
sec_long_term_total_16ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B16C3nkhlrsubbh
sec_long_term_total_1ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B1C3nkhlrsubbh
sec_long_term_total_2ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B2C3nkhlrsubbh
sec_long_term_total_3ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B3C3nkhlrsubbh
sec_long_term_total_4ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B4C3nkhlrsubbh
sec_long_term_total_5ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B5C3nkhlrsubbh
sec_long_term_total_6ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B6C3nkhlrsubbh
sec_long_term_total_7ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B7C3nkhlrsubbh
sec_long_term_total_8ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B8C3nkhlrsubbh
sec_long_term_total_9ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.LSEC.M176B9C3nkhlrsubbh
sec_total_10ACCUMULATIONINT8Counter shows the total number of log writing failures during the reporting period.LSEC.M176B10C1nkhlrsubbh
sec_total_11ACCUMULATIONINT8Counter shows the total number of command check errors during the reporting period.LSEC.M176B11C1nkhlrsubbh
sec_total_12ACCUMULATIONINT8Counter shows the total number of authentication failures during the reporting period.LSEC.M176B12C1nkhlrsubbh
sec_total_13ACCUMULATIONINT8Counter shows the total number of unknown IMSI numbers during the reporting period.LSEC.M176B13C1nkhlrsubbh
sec_total_14ACCUMULATIONINT8Counter shows the total number of IMEI numbers found to be on the black list during the reporting period.LSEC.M176B14C1nkhlrsubbh
sec_total_15ACCUMULATIONINT8Counter shows the total number of IMEI numbers found to be on the grey list during the reporting period.LSEC.M176B15C1nkhlrsubbh
sec_total_16ACCUMULATIONINT8Counter shows the total number of unknown IMEI numbers during the reporting period.LSEC.M176B16C1nkhlrsubbh
sec_total_1ACCUMULATIONINT8Counter shows the total number of successful events during the reporting period.LSEC.M176B1C1nkhlrsubbh
sec_total_2ACCUMULATIONINT8Counter shows the total number of illegal login attempts during the reporting period.LSEC.M176B2C1nkhlrsubbh
sec_total_3ACCUMULATIONINT8Counter shows the total number of successful events during the reporting period.LSEC.M176B3C1nkhlrsubbh
sec_total_4ACCUMULATIONINT8Counter shows the total number of attempts to access a network element with an invalid username or password during the reporting period.LSEC.M176B4C1nkhlrsubbh
sec_total_5ACCUMULATIONINT8Counter shows the total number of attempts to access a network element with inadequate access rights during the reporting period.LSEC.M176B5C1nkhlrsubbh
sec_total_6ACCUMULATIONINT8Counter shows the total number of started MML sessions during the reporting period.LSEC.M176B6C1nkhlrsubbh
sec_total_7ACCUMULATIONINT8Counter shows the total number of attempts to open an MML session with an invalid username or password during the reporting period.LSEC.M176B7C1nkhlrsubbh
sec_total_8ACCUMULATIONINT8Counter shows the total number of attempts to give MML commands with inadequate access rights during the reporting period.LSEC.M176B8C1nkhlrsubbh
sec_total_9ACCUMULATIONINT8Counter shows the total number of new usernames that have been created during the reporting period.LSEC.M176B9C1nkhlrsubbh
totalACCUMULATIONINT8This counter shows the total number of successful events during the reporting period.LSEC.M176B17C1nkhlrsubbh


HLR.Nokia.GSM.SGSN_Registered_Subscribers

This section describes the counters of M352

KPITypeData TypeDescriptionDerivationAdditional Summaries
missing_data_from_hlr0_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 0 has missing data.)SGSNH.M352B10C0 
missing_data_from_hlr1_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 1 has missing data.)SGSNH.M352B10C1 
missing_data_from_hlr10_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 10 has missing data.)SGSNH.M352B10C10 
missing_data_from_hlr11_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 11 has missing data.)SGSNH.M352B10C11 
missing_data_from_hlr12_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 12 has missing data.)SGSNH.M352B10C12 
missing_data_from_hlr13_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 13 has missing data.)SGSNH.M352B10C13 
missing_data_from_hlr14_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 14 has missing data.)SGSNH.M352B10C14 
missing_data_from_hlr15_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 15 has missing data.)SGSNH.M352B10C15 
missing_data_from_hlr2_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 2 has missing data.)SGSNH.M352B10C2 
missing_data_from_hlr3_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 3 has missing data.)SGSNH.M352B10C3 
missing_data_from_hlr4_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 4 has missing data.)SGSNH.M352B10C4 
missing_data_from_hlr5_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 5 has missing data.)SGSNH.M352B10C5 
missing_data_from_hlr6_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 6 has missing data.)SGSNH.M352B10C6 
missing_data_from_hlr7_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 7 has missing data.)SGSNH.M352B10C7 
missing_data_from_hlr8_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 8 has missing data.)SGSNH.M352B10C8 
missing_data_from_hlr9_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 9 has missing data.)SGSNH.M352B10C9 
number_of_answered_hlrusINTENSITYINTEGERNumber of HLRUs which responded to inquiry. This number can be different from the NUMBER OF HLRUS in the case when some of the HLRUs are temporarily out of order or they are overloaded. The field has effect on the rest of the reportSGSNH.M352B1C14 
number_of_hlrusINTENSITYINTEGERTotal number of HLRU pairs in HLR.SGSNH.M352B1C13 
restart_in_hlruINTENSITYINTEGERThis field indicates that duplex restart occurred in HLRU(s) during the measurement. The counters are unreliable. The field has effect on all report parts.SGSNH.M352B12C1 
restart_in_stuINTENSITYINTEGERThis field indicates that duplex restart occurred in STU(s) during the measurement. The counters are unreliable. The field has effect on all report part.SGSNH.M352B12C2 


HLR.Nokia.GSM.SPC_Authentication_Count

This table contains information about the AC measurement, which shows the number of the authentication triplets transferred from a specific VLR address. N.B. There is a secondary key of signalling_point

The performance data measurements for this KPI group are recorded against the combination of HLR and Signalling_Point (signalling_point_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
number_of_quintetsACCUMULATIONINT8(Obsolete in M13.5, ACHSPC block now supported under Signalling_Point object) The number of transferred authentication quintets.obsolete.obsoletenkhlrsubbh
number_of_syncreqACCUMULATIONINT8(Obsolete in M13.5, ACHSPC block now supported under Signalling_Point object) The number of synchronization requests which can be sent when the mobile rejects the authentication because the sequence number is out of range.obsolete.obsoletenkhlrsubbh
number_of_unknownsubscACCUMULATIONINT8(Obsolete in M13.5, ACHSPC block now supported under Signalling_Point object) The number of unknown subscribers whose data was not found in the ACobsolete.obsoletenkhlrsubbh
numberofansweredACCUMULATIONINT8(Obsolete in M13.5, ACHSPC block now supported under Signalling_Point object) The number of answers received to the VLR/SGSN authentication vector requests. These answers contain authentication vectors. If the number of requests is larger than the number of answers, the subscriber has not been created in the AC and the answer to the authentication vector request does not contain authentication vector. It is possible that the data on the subscribers location in the ACUs has not yet been updated after the system has been restarted.obsolete.obsoletenkhlrsubbh
numberofrequestsACCUMULATIONINT8(Obsolete in M13.5, ACHSPC block now supported under Signalling_Point object) The number of authentication vector (triplets and quintets) requests. This field also contains the synchronization requests. obsolete.obsoletenkhlrsubbh
numberoftripletsACCUMULATIONINT8(Obsolete in M13.5, ACHSPC block now supported under Signalling_Point object) The number of transferred authentication triplets.obsolete.obsoletenkhlrsubbh


HLR.Nokia.GSM.Subscribers_in_VLR

This section describes the counters of M84: MeO HLR / DEST. N.B. There is a secondary key of VLR address

The performance data measurements for this KPI group are recorded against the combination of HLR and VLR_Address (vlr_address_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ave_subsc_in_vlrINTENSITYFLOATThe average of own network subscribers in the VLR of another networkVLRME.M84B9C3 
hlr_unreliableINTENSITYINTEGERThis counter can appear in the XML report with value 1 when the Average Number of Subscribers counter is unreliable (there were a VLR address cleaning in the HLR database during the measurement which causes a special problem in the procedure of the gathering average counters, however this is a rare situation)VLRME.M84B11C1 
subsc_in_vlrINTENSITYINT8The number of subscribers in the VLRVLRME.M84B9C2 


HLR.Nokia.GSM.Supplementary_Services

This section describes the counters of M79: MeO HLR / SSERVICE. N.B. There is a secondary key of supplementary_service

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
count_prov_servINTENSITYINTEGERThe number of supplementary services that are provisioned for subscribers.SSERV.M79B4C2nkhlrsubbh
count_serv_act_mmlACCUMULATIONINT8The count of services activated by MML.SSERV.M79B4C3nkhlrsubbh
count_serv_act_userACCUMULATIONINT8The count of services activated by the user.SSERV.M79B4C4nkhlrsubbh
count_serv_deact_mmlACCUMULATIONINT8The count of services deactivated by MML.SSERV.M79B4C5nkhlrsubbh
count_serv_deact_userACCUMULATIONINT8The count of services deactivated by the user.SSERV.M79B4C6nkhlrsubbh
count_serv_inq_userACCUMULATIONINT8The count of services inquired by the user.SSERV.M79B4C8nkhlrsubbh


HLR.Nokia.GSM.TCAP_Messages

This table contains measurement data of one or more signalling links in the transaction capabilities application part.Related to messages

KPITypeData TypeDescriptionDerivationAdditional Summaries
msg_discardedACCUMULATIONINT8The number of messages discardedTCAPHLR.M220B5C2nkhlrsubbh
received_abortACCUMULATIONINT8The number of received ABORT messagesTCAPHLR.M220B6C10nkhlrsubbh
received_beginACCUMULATIONINT8The number of received BEGIN messagesTCAPHLR.M220B6C4nkhlrsubbh
received_continueACCUMULATIONINT8The number of received CONTINUE messagesTCAPHLR.M220B6C6nkhlrsubbh
received_endACCUMULATIONINT8The number of received END messagesTCAPHLR.M220B6C8nkhlrsubbh
received_unidirectionalACCUMULATIONINT8The number of received UNIDIRECTIONAL messagesTCAPHLR.M220B6C2nkhlrsubbh
tc_total_receivedACCUMULATIONINT8The number of received UNIDIRECTIONAL messagesTCAPHLR.M220B6C12nkhlrsubbh
tc_total_transACCUMULATIONINT8The number of transmitted UNIDIRECTIONAL messagesTCAPHLR.M220B6C11nkhlrsubbh
trans_abortACCUMULATIONINT8The number of transmitted ABORT messagesTCAPHLR.M220B6C9nkhlrsubbh
trans_beginACCUMULATIONINT8The number of transmitted BEGIN messagesTCAPHLR.M220B6C3nkhlrsubbh
trans_continueACCUMULATIONINT8The number of transmitted CONTINUE messagesTCAPHLR.M220B6C5nkhlrsubbh
trans_endACCUMULATIONINT8The number of transmitted END messagesTCAPHLR.M220B6C7nkhlrsubbh
trans_unidirectionalACCUMULATIONINT8The number of transmitted UNIDIRECTIONAL messagesTCAPHLR.M220B6C1nkhlrsubbh


HLR.Nokia.GSM.TCAP_Performance

This table contains measurement data of one or more signalling links in the transaction capabilities application part.

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_transactionACCUMULATIONINT8The number of errors detected in the transaction portionTCAPHLR.M220B5C5nkhlrsubbh
pa_receivedACCUMULATIONINT8The number of provider aborts receivedTCAPHLR.M220B5C3nkhlrsubbh
received_tc_componentsACCUMULATIONINT8The number of received TC componentsTCAPHLR.M220B6C14nkhlrsubbh
rej_receivedACCUMULATIONINT8The number of rejects receivedTCAPHLR.M220B5C4nkhlrsubbh
tcl_cancelACCUMULATIONINT8The number of received TCL cancel indications for class 1 operationsTCAPHLR.M220B5C1nkhlrsubbh
trans_tc_componentsACCUMULATIONINT8The number of transmitted TC componentsTCAPHLR.M220B6C13nkhlrsubbh


HLR.Nokia.GSM.TCAP_Protocol_Error_In_Completion_Portion

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to protocol errors in the completion portion.

KPITypeData TypeDescriptionDerivationAdditional Summaries
comp_received_bad_structureACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: badly structured componentTCAPHLR.M220B3C5nkhlrsubbh
comp_received_mistypedACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: mistyped componentTCAPHLR.M220B3C3nkhlrsubbh
comp_received_ret_errorACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: return error unexpectedTCAPHLR.M220B3C15nkhlrsubbh
comp_received_ret_resultACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: return result unexpectedTCAPHLR.M220B3C11nkhlrsubbh
comp_received_unrecognizedACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: unrecognised componentTCAPHLR.M220B3C1nkhlrsubbh
comp_trans_bad_structureACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: badly structured componentTCAPHLR.M220B3C6nkhlrsubbh
comp_trans_mistypedACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: mistyped componentTCAPHLR.M220B3C4nkhlrsubbh
comp_trans_ret_errorACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: return error unexpectedTCAPHLR.M220B3C16nkhlrsubbh
comp_trans_unrecognizedACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: unrecognised componentTCAPHLR.M220B3C2nkhlrsubbh
reject_rxed_unrec_invoke_id_reACCUMULATIONINT8Protocol error in comp. portion (reject rec.)-problem code: unrecognized invoke id. (RE)TCAPHLR.M220B3C13nkhlrsubbh
reject_rxed_unrec_invoke_id_rrACCUMULATIONINT8Protocol error in comp. portion (reject rec.)- problem code: unrecognized invoke id. (RR)TCAPHLR.M220B3C9nkhlrsubbh
reject_rxed_unrec_linked_idACCUMULATIONINT8Protocol error in comp. portion (reject rec.)- problem code: unrecognized linked id. TCAPHLR.M220B3C7nkhlrsubbh
reject_sent_return_result_unexACCUMULATIONINT8Protocol error in comp. portion (reject sent)-problem code: return result unexpected TCAPHLR.M220B3C12nkhlrsubbh
reject_sent_unrec_invoke_id_reACCUMULATIONINT8Protocol error in comp. portion (reject sent)- problem code: unrecognized invoke id. (RE)TCAPHLR.M220B3C14nkhlrsubbh
reject_sent_unrec_invoke_id_rrACCUMULATIONINT8Protocol error in comp. portion (reject sent)-problem code: unrecognized invoke id. (RR)TCAPHLR.M220B3C10nkhlrsubbh
reject_sent_unrec_linked_idACCUMULATIONINT8Protocol error in comp. portion (reject sent)- problem code: unrecognized linked idTCAPHLR.M220B3C8nkhlrsubbh


HLR.Nokia.GSM.TCAP_Protocol_Error_In_Transaction_Portion

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to protocol errors in the transaction portion.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ab_received_msg_typeACCUMULATIONINT8Protocol error in transaction portion (abort received) - unrecognised message typeTCAPHLR.M220B2C1nkhlrsubbh
ab_received_rlimitACCUMULATIONINT8Protocol error in transaction portion (abort received) - resource limitationTCAPHLR.M220B2C9nkhlrsubbh
ab_received_ta_bad_formatACCUMULATIONINT8Protocol error in transaction portion (abort received) - badly formatted transaction portionTCAPHLR.M220B2C5nkhlrsubbh
ab_received_ta_incorrectACCUMULATIONINT8Protocol error in transaction portion (abort received) - incorrect transaction portionTCAPHLR.M220B2C3nkhlrsubbh
ab_received_ta_unrecognizedACCUMULATIONINT8Protocol error in transaction portion (abort received) - unrecognized transaction identifierTCAPHLR.M220B2C7nkhlrsubbh
ab_trans_msg_typeACCUMULATIONINT8Protocol error in transaction portion (abort sent) - unrecognised message typeTCAPHLR.M220B2C2nkhlrsubbh
ab_trans_rlimitACCUMULATIONINT8Protocol error in transaction portion (abort sent) - resource limitationTCAPHLR.M220B2C10nkhlrsubbh
ab_trans_ta_bad_formatACCUMULATIONINT8Protocol error in transaction portion (abort sent) - badly formatted transaction portionTCAPHLR.M220B2C6nkhlrsubbh
ab_trans_ta_incorrectACCUMULATIONINT8Protocol error in transaction portion (abort sent) - incorrect transaction portionTCAPHLR.M220B2C4nkhlrsubbh
ab_trans_ta_unrecognizedACCUMULATIONINT8Protocol error in transaction portion (abort sent) - unrecognised transaction identifierTCAPHLR.M220B2C8nkhlrsubbh


HLR.Nokia.GSM.TCAP_Transaction

This section describes the TC transactions meters measurement.N.B. There is a secondary key of signalling_network and also of subsystem

The performance data measurements for this KPI group are recorded against the combination of HLR, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
max_openINTENSITYINTEGERMaximum number of open transaction Ids during the periodTTRAHLR.M224B2C4nkhlrsubbh
mean_durationINTENSITYINTEGERCumulative mean duration of transactionsTTRAHLR.M224B2C3nkhlrsubbh
newACCUMULATIONINT8The number of new transactions during the periodTTRAHLR.M224B2C1nkhlrsubbh
openINTENSITYINTEGERMean number of open transaction Ids during the periodTTRAHLR.M224B2C2nkhlrsubbh


HLR.Nokia.GSM.TCAP_User_Generated_Problems

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to user generated problems

KPITypeData TypeDescriptionDerivationAdditional Summaries
reject_rxed_duplic_invoke_idACCUMULATIONINT8TC user generated problem (Reject received) - duplicate invoke id. ( 14.3a in ITU-T Q.752 )TCAPHLR.M220B4C1nkhlrsubbh
reject_sent_duplic_invoke_idACCUMULATIONINT8TC user generated problem (Reject sent) -duplicate invoke id. ( 14.6a in ITU-T Q.752 )TCAPHLR.M220B4C2nkhlrsubbh
tc_received_init_releaseACCUMULATIONINT8TC user generated problem (reject rec.) problem code: initiating releaseTCAPHLR.M220B4C9nkhlrsubbh
tc_received_link_op_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unexpected link operationTCAPHLR.M220B4C13nkhlrsubbh
tc_received_link_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: link response unexpectedTCAPHLR.M220B4C11nkhlrsubbh
tc_received_mistyped_paramACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameterTCAPHLR.M220B4C5nkhlrsubbh
tc_received_mistyped_reACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameter (RE)TCAPHLR.M220B4C21nkhlrsubbh
tc_received_mistyped_rrACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameter (RR)TCAPHLR.M220B4C19nkhlrsubbh
tc_received_rlimitACCUMULATIONINT8TC user generated problem (reject rec.) problem code: resource limitationTCAPHLR.M220B4C7nkhlrsubbh
tc_received_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unexpected errorTCAPHLR.M220B4C17nkhlrsubbh
tc_received_unknown_opACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unrecognised operationTCAPHLR.M220B4C3nkhlrsubbh
tc_received_unrecognizedACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unrecognised errorTCAPHLR.M220B4C15nkhlrsubbh
tc_trans_init_releaseACCUMULATIONINT8TC user generated problem (reject sent.) problem code: initiating releaseTCAPHLR.M220B4C10nkhlrsubbh
tc_trans_link_op_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unexpected link operationTCAPHLR.M220B4C14nkhlrsubbh
tc_trans_link_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: link response unexpectedTCAPHLR.M220B4C12nkhlrsubbh
tc_trans_mistyped_paramACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameterTCAPHLR.M220B4C6nkhlrsubbh
tc_trans_mistyped_reACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameter (RE)TCAPHLR.M220B4C22nkhlrsubbh
tc_trans_mistyped_rrACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameter (RR)TCAPHLR.M220B4C20nkhlrsubbh
tc_trans_rlimitACCUMULATIONINT8TC user generated problem (reject sent.) problem code: resource limitationTCAPHLR.M220B4C8nkhlrsubbh
tc_trans_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unexpected errorTCAPHLR.M220B4C18nkhlrsubbh
tc_trans_unknown_opACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unrecognised operationTCAPHLR.M220B4C4nkhlrsubbh
tc_trans_unrecognizedACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unrecognised errorTCAPHLR.M220B4C16nkhlrsubbh


HLR.Nokia.GSM.VLR

This measurement table contains information on the number of HLRUs in the HLR

KPITypeData TypeDescriptionDerivationAdditional Summaries
missing_data_from_hlr0_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 0 has missing data.)HLRVLR.M84B10C0nkhlrsubbh
missing_data_from_hlr1_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 1 has missing data.)HLRVLR.M84B10C1nkhlrsubbh
missing_data_from_hlr10_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 10 has missing data.)HLRVLR.M84B10C10nkhlrsubbh
missing_data_from_hlr11_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 11 has missing data.)HLRVLR.M84B10C11nkhlrsubbh
missing_data_from_hlr12_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 12 has missing data.)HLRVLR.M84B10C12nkhlrsubbh
missing_data_from_hlr13_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 13 has missing data.)HLRVLR.M84B10C13nkhlrsubbh
missing_data_from_hlr14_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 14 has missing data.)HLRVLR.M84B10C14nkhlrsubbh
missing_data_from_hlr15_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 15 has missing data.)HLRVLR.M84B10C15nkhlrsubbh
missing_data_from_hlr2_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 2 has missing data.)HLRVLR.M84B10C2nkhlrsubbh
missing_data_from_hlr3_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 3 has missing data.)HLRVLR.M84B10C3nkhlrsubbh
missing_data_from_hlr4_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 4 has missing data.)HLRVLR.M84B10C4nkhlrsubbh
missing_data_from_hlr5_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 5 has missing data.)HLRVLR.M84B10C5nkhlrsubbh
missing_data_from_hlr6_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 6 has missing data.)HLRVLR.M84B10C6nkhlrsubbh
missing_data_from_hlr7_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 7 has missing data.)HLRVLR.M84B10C7nkhlrsubbh
missing_data_from_hlr8_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 8 has missing data.)HLRVLR.M84B10C8nkhlrsubbh
missing_data_from_hlr9_if_value_is_1INTENSITYINTEGERIf a message (data) from some HLRU is missing, the identity of the HLRU is shown in the list. It is possible that the NUMBER OF ANSWERED HLRUS equals with the NUMBER OF HLRUS but this field shows some missing data. The field has effect on the rest of the report. (The text appears only in case of missing data. Value can be 1 or 0 due to HLRU no. 9 has missing data.)HLRVLR.M84B10C9nkhlrsubbh
nbr_of_hlru_dataINTENSITYINTEGERNumber of HLRUs in the HLR that have sent dataHLRVLR.M84B1C14nkhlrsubbh
nbr_of_hlruINTENSITYINTEGERNumber of HLRUs in the HLR.HLRVLR.M84B1C13nkhlrsubbh
restart_in_hlruINTENSITYINTEGERThis field indicates that duplex restart occurred in HLRU(s) during the measurement. The counters are unreliable. The field has effect on all report parts.HLRVLR.M84B12C1nkhlrsubbh
restart_in_stuINTENSITYINTEGERThis field indicates that duplex restart occurred in STU(s) during the measurement. The counters are unreliable. The field has effect on all report part.HLRVLR.M84B12C2nkhlrsubbh
tot_ave_subscINTENSITYINTEGERTotal average number of subscribers in all VLRs.HLRVLR.M84B9C5nkhlrsubbh
tot_curr_subscINTENSITYINTEGERTotal current number of subscribers in all VLRs.HLRVLR.M84B9C4nkhlrsubbh
unreliabletotalaveragesubscrINTENSITYINTEGERThis counter can appear in the XML report with value 1 when any of the Average Number of Subscribers counters was unreliable (there were a VLR address cleaning in the HLR database during the measurement which causes a special problem in the procedure of the gathering average counters, however this is a rare situation)HLRVLR.M84B11C2nkhlrsubbh


HLR_Destination Performance Indicators

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


HLR_Destination.Nokia.GSM.INAP_Invocation

INAP invocations

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_DP_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement during the measurement period had been restarted and thus data might be missing from the measurement.IDPHDES.M199B1C1 or IDPHSN.M199B1C1nkhlrsubbh
INAP_DP_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed INAP invocations during the measurement period.IDPHDES.M199B1C4 or IDPHSN.M199B1C4nkhlrsubbh
INAP_DP_SUM_STARTEDACCUMULATIONINT8Shows the total number of started INAP invocations during the measurement period.IDPHDES.M199B1C3 or IDPHSN.M199B1C3nkhlrsubbh


HLR_Destination.Nokia.GSM.INAP_Reject

INAP rejects

The performance data measurements for this KPI group are recorded against the combination of HLR_Destination and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.IOC2HDRC.M194B5C1 or IOC2HSRC.M194B5C1nkhlrsubbh
INAP_OOC_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.IOCOHDRC.M195B5C1 or IOCOHSRC.M195B5C1nkhlrsubbh


HLR_Destination.Nokia.GSM.Incoming_INAP_Application_Context

Incoming INAP application context statistics

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_IAC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful incoming INAP application contexts during the measurement period.percentok(({INAP_IAC_SUM_STARTED} - {INAP_IAC_SUM_FAILED}), ({INAP_IAC_SUM_SUCCEEDED}))nkhlrsubbh
INAP_IAC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement during the measurement period had been restarted, and thus data might be missing from the measurement.IACIHDES.M196B1C1 or IACIHSN.M196B1C1nkhlrsubbh
INAP_IAC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming INAP application contexts during the measurement period.IACIHDES.M196B1C5 or IACIHSN.M196B1C5nkhlrsubbh
INAP_IAC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming INAP application contexts during the measurement period.IACIHDES.M196B1C3 or IACIHSN.M196B1C3nkhlrsubbh
INAP_IAC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming INAP application contexts during the measurement period.IACIHDES.M196B1C4 or IACIHSN.M196B1C4nkhlrsubbh


HLR_Destination.Nokia.GSM.Incoming_INAP_Operation_Part1

Incoming INAP Operations for report part1

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC1_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement during the measurement period, had been restarted and thus data might be missing from the measurement.IOC1HDES.M193B1C1 or IOC1HSN.M193B1C1nkhlrsubbh
INAP_IOC1_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming INAP operations (in the report part) during the measurement period.IOC1HDES.M193B1C5 or IOC1HSN.M193B1C5nkhlrsubbh
INAP_IOC1_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming INAP operations (in the report part) during the measurement period.IOC1HDES.M193B1C3 or IOC1HSN.M193B1C3nkhlrsubbh
INAP_IOC1_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming INAP operations (in the report part) during the measurement period.IOC1HDES.M193B1C4 or IOC1HSN.M193B1C4nkhlrsubbh


HLR_Destination.Nokia.GSM.Incoming_INAP_Operation_Part2

Incoming INAP Operations for report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_IOC2_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful incoming INAP operations (in the report part) during the measurement period.percentok(({HLR_Destination.Nokia.GSM.Incoming_INAP_Operation_Part1.INAP_IOC1_SUM_SUCCEEDED} + {INAP_IOC2_SUM_SUCCEEDED}), ({HLR_Destination.Nokia.GSM.Incoming_INAP_Operation_Part1.INAP_IOC1_SUM_STARTED} + {INAP_IOC2_SUM_STARTED}))nkhlrsubbh
INAP_IOC2_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.IOC2HDES.M194B1C1 or IOC2HSN.M194B1C1nkhlrsubbh
INAP_IOC2_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming INAP operations (in the report part) during the measurement period.IOC2HDES.M194B1C5 or IOC2HSN.M194B1C5nkhlrsubbh
INAP_IOC2_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming INAP operations (in the report part) during the measurement period.IOC2HDES.M194B1C3 or IOC2HSN.M194B1C3nkhlrsubbh
INAP_IOC2_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming INAP operations (in the report part) during the measurement period.IOC2HDES.M194B1C4 or IOC2HSN.M194B1C4nkhlrsubbh


HLR_Destination.Nokia.GSM.Outgoing_INAP_Application_Context

Incoming INAP application context statistics

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_OAC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful outgoing INAP application contexts during the measurement period.percentok(({INAP_OAC_SUM_STARTED} - {INAP_OAC_SUM_FAILED}), ({INAP_OAC_SUM_SUCCEEDED}))nkhlrsubbh
INAP_OAC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.IACOHDES.M197B1C1 or IACOHSN.M197B1C1nkhlrsubbh
INAP_OAC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed outgoing INAP application contexts during the measurement period.IACOHDES.M197B1C5 or IACOHSN.M197B1C5nkhlrsubbh
INAP_OAC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started outgoing INAP application contexts during the measurement period.IACOHDES.M197B1C3 or IACOHSN.M197B1C3nkhlrsubbh
INAP_OAC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded outgoing INAP application contexts during the measurement period.IACOHDES.M197B1C4 or IACOHSN.M197B1C4nkhlrsubbh


HLR_Destination.Nokia.GSM.Outgoing_INAP_Operation

Outgoing INAP Operation stats

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_OOC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful outgoing INAP operations during the measurement period.percentok(({INAP_OOC_SUM_STARTED} - {INAP_OOC_SUM_FAILED}), ({INAP_OOC_SUM_SUCCEEDED}))nkhlrsubbh
INAP_OOC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.IOCOHDES.M195B1C1 or IOCOHSN.M195B1C1nkhlrsubbh
INAP_OOC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed outgoing INAP operations during the measurement period.IOCOHDES.M195B1C5 or IOCOHSN.M195B1C5nkhlrsubbh
INAP_OOC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started outgoing INAP operations during the measurement period.IOCOHDES.M195B1C3 or IOCOHSN.M195B1C3nkhlrsubbh
INAP_OOC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded outgoing INAP operations during the measurement period.IOCOHDES.M195B1C4 or IOCOHSN.M195B1C4nkhlrsubbh


HLR_Destination.Nokia.GSM.SSAP_Dialogue

SSAP Dialogue

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_DI_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.SSAPHSUB.M198B1C1nkhlrsubbh
SSAP_DI_SUM_FAILED_INACCUMULATIONINT8Shows the total number of failed incoming SSAP dialogues during the measurement period.SSAPHSUB.M198B1C5nkhlrsubbh
SSAP_DI_SUM_FAILED_OUTACCUMULATIONINT8Shows the total number of failed outgoing SSAP dialogues during the measurement period.SSAPHSUB.M198B1C6nkhlrsubbh
SSAP_DI_SUM_STARTED_INACCUMULATIONINT8Shows the total number of started incoming SSAP dialogues during the measurement period.SSAPHSUB.M198B1C3nkhlrsubbh
SSAP_DI_SUM_STARTED_OUTACCUMULATIONINT8Shows the total number of started outgoing SSAP dialogues during the measurement period.SSAPHSUB.M198B1C4nkhlrsubbh


HLR_Destination.Nokia.GSM.SSAP_Operation_Code

SSAP Operations

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_SSAP_OC_SUCCEEDED_OUTPERCENTAGEFLOATShows the percentage of successful outgoing SSAP operations during the measurement period.percentok(({SSAP_OC_SUM_STARTED_IN} + {SSAP_OC_SUM_STARTED_OUT} - {SSAP_OC_SUM_FAILED_IN} - {SSAP_OC_SUM_FAILED_IN}), ({SSAP_OC_SUM_STARTED_IN} + {SSAP_OC_SUM_STARTED_OUT}))nkhlrsubbh
SSAP_OC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.SSAPHSUB.M198B0C1nkhlrsubbh
SSAP_OC_SUM_FAILED_INACCUMULATIONINT8Shows the total number of failed incoming SSAP operations during the measurement period.SSAPHSUB.M198B0C5nkhlrsubbh
SSAP_OC_SUM_FAILED_OUTACCUMULATIONINT8Shows the total number of failed outgoing SSAP operations during the measurement period.SSAPHSUB.M198B0C6nkhlrsubbh
SSAP_OC_SUM_STARTED_INACCUMULATIONINT8Shows the total number of started incoming SSAP operations during the measurement period.SSAPHSUB.M198B0C3nkhlrsubbh
SSAP_OC_SUM_STARTED_OUTACCUMULATIONINT8Shows the total number of started outgoing SSAP operations during the measurement period.SSAPHSUB.M198B0C4nkhlrsubbh


HLR_Destination.Nokia.GSM.SSAP_Reject

SSAP rejects

The performance data measurements for this KPI group are recorded against the combination of HLR_Destination and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.SSAPHSRC.M198B5C1nkhlrsubbh


HLR_INAP_Application_Context Performance Indicators

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


HLR_INAP_Application_Context.Nokia.GSM.Incoming_Session

Incoming Session counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IAC_ABORT_TOTALACCUMULATIONINT8Shows the number of application context interruptions during the measurement period.{INAP_IAC_USER_ABORT} + {INAP_IAC_INTERNAL_ABORT} + {INAP_IAC_TCAP_USER_ABORT} + {INAP_IAC_TCAP_PROVIDER_ABORT} + {INAP_IAC_CANCELLED} + {INAP_IAC_TIMER_EXPIRATION}nkhlrsubbh
INAP_IAC_CANCELLEDACCUMULATIONINT8Shows the number of application context interruptions caused by TCAP time supervision expiration during the measurement period.IACIHDAC.M196B3C6 or IACIHSAC.M196B3C6nkhlrsubbh
INAP_IAC_INTERNAL_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by INAP itself during the measurement period.IACIHDAC.M196B3C3 or IACIHSAC.M196B3C3nkhlrsubbh
INAP_IAC_STARTEDACCUMULATIONINT8Shows the number of started INAP application contexts during the measurement period.IACIHDAC.M196B3C1 or IACIHSAC.M196B3C1nkhlrsubbh
INAP_IAC_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the TCAP in the SSP or SCP during the measurement period.IACIHDAC.M196B3C5 or IACIHSAC.M196B3C5nkhlrsubbh
INAP_IAC_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the receiving INAP entity during the measurement period.IACIHDAC.M196B3C4 or IACIHSAC.M196B3C4nkhlrsubbh
INAP_IAC_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of application context interruptions caused by the expiration of INAP internal time supervision during the measurement period.IACIHDAC.M196B3C7 or IACIHSAC.M196B3C7nkhlrsubbh
INAP_IAC_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the INAP user during the measurement period.IACIHDAC.M196B3C2 or IACIHSAC.M196B3C2nkhlrsubbh


HLR_INAP_Application_Context.Nokia.GSM.Outgoing_Session

Outgoing Session Counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OAC_ABORT_TOTALACCUMULATIONINT8Shows the number of application context interruptions during the measurement period.{INAP_OAC_USER_ABORT} + {INAP_OAC_INTERNAL_ABORT} + {INAP_OAC_TCAP_USER_ABORT} + {INAP_OAC_TCAP_PROVIDER_ABORT} + {INAP_OAC_CANCELLED} + {INAP_OAC_TIMER_EXPIRATION}nkhlrsubbh
INAP_OAC_CANCELLEDACCUMULATIONINT8Shows the number of application context interruptions caused by the expiration of TCAP time supervision during the measurement period.IACOHDAC.M197B3C6 or IACOHSAC.M197B3C6nkhlrsubbh
INAP_OAC_INTERNAL_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the INAP itself during the measurement period.IACOHDAC.M197B3C3 or IACOHSAC.M197B3C3nkhlrsubbh
INAP_OAC_STARTEDACCUMULATIONINT8Shows the number of started INAP application contexts during the measurement period.IACOHDAC.M197B3C1 or IACOHSAC.M197B3C1nkhlrsubbh
INAP_OAC_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the TCAP in the SSP or SCP during the measurement period.IACOHDAC.M197B3C5 or IACOHSAC.M197B3C5nkhlrsubbh
INAP_OAC_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the receiving INAP entity during the measurement period.IACOHDAC.M197B3C4 or IACOHSAC.M197B3C4nkhlrsubbh
INAP_OAC_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of application context interruptions caused by the expiration of INAP internal time supervision during the measurement period.IACOHDAC.M197B3C7 or IACOHSAC.M197B3C7nkhlrsubbh
INAP_OAC_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the INAP user during the measurement period.IACOHDAC.M197B3C2 or IACOHSAC.M197B3C2nkhlrsubbh


HLR_INAP_Detection_Point Performance Indicators

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


HLR_INAP_Detection_Point.Nokia.GSM.INAP_Service_Invocation

INAP service Invocations

The performance data measurements for this KPI group are recorded against the combination of HLR_INAP_Detection_Point and IN_Service (in_service_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_DP_FAILED_INVOCATIONSACCUMULATIONINT8Shows the number of failed service keys during the measurement period.IDPHD.M199B3C2 or IDPHS.M199B3C2nkhlrsubbh
INAP_DP_STARTED_INVOCATIONSACCUMULATIONINT8Shows the number of started service keys during the measurement period.IDPHD.M199B3C1 or IDPHS.M199B3C1nkhlrsubbh


HLR_INAP_Error_Code Performance Indicators

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


HLR_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part1

Incoming terminations report Part1

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC1_EC_NUMBERACCUMULATIONINT8The number of INAP operations terminated due to error during the measurement period.IOC1HDEC.M193B4C1 or IOC1HSEC.M193B4C1nkhlrsubbh


HLR_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part2

Incoming terminations report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_EC_NUMBERACCUMULATIONINT8Shows the number of INAP operations terminated due to an error during the measurement period.IOC2HSEC.M194B4C1 or IOC2HDEC.M194B4C1nkhlrsubbh


HLR_INAP_Error_Code.Nokia.GSM.Outgoing_Termination

Outgoing Terminations

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OOC_EC_NUMBERACCUMULATIONINT8Shows the number of INAP operations terminated due to error during the measurement period.IOCOHDEC.M195B4C1 or IOCOHSEC.M195B4C1nkhlrsubbh


HLR_INAP_Op_Code Performance Indicators

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


HLR_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part1

Incoming session report part1

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC1_ABORTEDACCUMULATIONINT8Shows TCAP user,the number of aborted INAP operations due to internal errors or provider aborts during the measurement period.IOC1HDOC.M193B3C3 or IOC1HSOC.M193B3C3 or IOC2HDOC.M193B3C3 or IOCOHDOC.M193B3C3 or IOCOHSOC.M193B3C3nkhlrsubbh
INAP_IOC1_CANCELLEDACCUMULATIONINT8Shows the number of INAP operations cancelled due to timer expirations on different levels during the measurement period.IOC1HDOC.M193B3C5 or IOC1HSOC.M193B3C5 or IOC2HDOC.M193B3C5 or IOCOHDOC.M193B3C5 or IOCOHSOC.M193B3C5nkhlrsubbh
INAP_IOC1_ERRORSACCUMULATIONINT8Shows the number of INAP operations terminated by an error during the measurement period.IOC1HDOC.M193B3C2 or IOC1HSOC.M193B3C2 or IOC2HDOC.M193B3C2 or IOCOHDOC.M193B3C2 or IOCOHSOC.M193B3C2nkhlrsubbh
INAP_IOC1_REJECTEDACCUMULATIONINT8Shows the rejected INAP operations during the measurement period. It can be rejected by TCAP user of the remote end, by TCAP of the remote end, or by the near end TCAP.IOC1HDOC.M193B3C4 or IOC1HSOC.M193B3C4 or IOC2HDOC.M193B3C4 or IOCOHDOC.M193B3C4 or IOCOHSOC.M193B3C4nkhlrsubbh
INAP_IOC1_STARTEDACCUMULATIONINT8Shows the number of started INAP operations during the measurement period.IOC1HDOC.M193B3C1 or IOC1HSOC.M193B3C1 or IOC2HDOC.M193B3C1 or IOCOHDOC.M193B3C1 or IOCOHSOC.M193B3C1nkhlrsubbh


HLR_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part2

Incoming session report part2

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_ABORTEDACCUMULATIONINT8Shows the TCAP user, the number of aborted INAP operations due to internal errors or provider aborts during the measurement period.IOC2HDOC.M194B3C3 or IOC2HSOC.M194B3C3nkhlrsubbh
INAP_IOC2_CANCELLEDACCUMULATIONINT8Shows the number of INAP operations cancelled due to timer expirations on different levels during the measurement period.IOC2HDOC.M194B3C5 or IOC2HSOC.M194B3C5nkhlrsubbh
INAP_IOC2_ERRORSACCUMULATIONINT8Shows the number of INAP operations terminated by an error during the measurement period.IOC2HDOC.M194B3C2 or IOC2HSOC.M194B3C2nkhlrsubbh
INAP_IOC2_REJECTEDACCUMULATIONINT8Shows the rejected INAP operations during the measurement period. It can be rejected by TCAP user of the remote end, by TCAP of the remote end, or by the near end TCAP.IOC2HDOC.M194B3C4 or IOC2HSOC.M194B3C4nkhlrsubbh
INAP_IOC2_STARTEDACCUMULATIONINT8Shows the number of started INAP operations during the measurement period.IOC2HDOC.M194B3C1 or IOC2HSOC.M194B3C1nkhlrsubbh


HLR_INAP_Op_Code.Nokia.GSM.Outgoing_Session

Outgoing session counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OOC_ABORTEDACCUMULATIONINT8Shows the TCAP user, the number of aborted INAP operations due to internal errors or provider aborts during the measurement period.IOCOHDOC.M195B3C3 or IOCOHSOC.M195B3C3nkhlrsubbh
INAP_OOC_CANCELLEDACCUMULATIONINT8Shows the number of INAP operations cancelled due to timer expirations on different levels during the measurement period.IOCOHDOC.M195B3C5 or IOCOHSOC.M195B3C5nkhlrsubbh
INAP_OOC_ERRORSACCUMULATIONINT8Shows the number of INAP operations terminated by an error during the measurement period.IOCOHDOC.M195B3C2 or IOCOHSOC.M195B3C2nkhlrsubbh
INAP_OOC_REJECTEDACCUMULATIONINT8Shows the rejected INAP operations during the measurement period. It can be rejected by TCAP user of the remote end, by the TCAP of the remote end, or by the near end TCAP.IOCOHDOC.M195B3C4 or IOCOHSOC.M195B3C4nkhlrsubbh
INAP_OOC_STARTEDACCUMULATIONINT8Shows the number of started INAP operations during the measurement period.IOCOHDOC.M195B3C1 or IOCOHSOC.M195B3C1nkhlrsubbh


HLR_SSAP_Dialogue Performance Indicators

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


HLR_SSAP_Dialogue.Nokia.GSM.Session

SSAP session counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_DI_CANCELLEDACCUMULATIONINT8Shows the number of cancelled SSAP dialogues (interruptions caused by the expiration of TCAP time supervision) during the measurement period.SSAPHSDI.M198B6C5nkhlrsubbh
SSAP_DI_OWN_ABORTACCUMULATIONINT8Shows the number of SSAP dialogues aborted by the SSAP itself during the measurement period.SSAPHSDI.M198B6C2nkhlrsubbh
SSAP_DI_STARTEDACCUMULATIONINT8Shows the number of started SSAP dialogues during the measurement period.SSAPHSDI.M198B6C1nkhlrsubbh
SSAP_DI_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of SSAP dialogues aborted by the TCAP in the source or destination network element during the measurement period.SSAPHSDI.M198B6C4nkhlrsubbh
SSAP_DI_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of SSAP dialogues aborted by the receiving SSAP entity during the measurement period.SSAPHSDI.M198B6C3nkhlrsubbh
SSAP_DI_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of interrupted SSAP dialogues caused by the expiration of SSAP internal time supervision during the measurement period.SSAPHSDI.M198B6C6nkhlrsubbh


HLR_SSAP_Operation Performance Indicators

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


HLR_SSAP_Operation.Nokia.GSM.Session

SSAP Operation counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_OC_ABORTEDACCUMULATIONINT8Shows the number of aborted SSAP operations due to internal errors or due to TCAP user or provider aborts during the measurement period.SSAPHSOC.M198B4C11nkhlrsubbh
SSAP_OC_CANCELLEDACCUMULATIONINT8Shows the number of cancelled SSAP operations during the measurement period (number of operations cancelled due to timer expirations on different levels).SSAPHSOC.M198B4C13nkhlrsubbh
SSAP_OC_CAUSED_BY_T3ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T3 during the measurement period.The maximum time, the service was available in the originating network, is expired.SSAPHSOC.M198B4C2nkhlrsubbh
SSAP_OC_CAUSED_BY_T4ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T4 during the measurement period.The maximum time that the originating network waits for user A to respond to a CCBS or CCNR recall, is expired.SSAPHSOC.M198B4C3nkhlrsubbh
SSAP_OC_CAUSED_BY_T7ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T7 during the measurement period.The lifetime of CCBS or CCNR request expired in the destination network.SSAPHSOC.M198B4C4nkhlrsubbh
SSAP_OC_CAUSED_BY_T9ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T9 during the measurement period.The maximum time, destination B waits for the CCBS call, when destination B has sent indication of remoteUserFree to the originating destination is expired.SSAPHSOC.M198B4C5nkhlrsubbh
SSAP_OC_ERRORSACCUMULATIONINT8Shows the number of SSAP operations with an error result during the measurement period. The detailed error reason is also presented where applicable. Errors can occur on application level, or on the application protocol level, or they can indicate a negative result.SSAPHSOC.M198B4C7nkhlrsubbh
SSAP_OC_LONG_TERM_DENIALACCUMULATIONINT8Shows the number of SSAP operations rejected because of LongTermDenial during the measurement period.The request to activate CCBS or CCNR has been rejected and most likely other following requests towards the same target user will be rejected.SSAPHSOC.M198B4C9nkhlrsubbh
SSAP_OC_REJECTEDACCUMULATIONINT8Shows the number of rejected SSAP operations during the measurement period. The operations can be rejected by the TCAP user of the remote end, by the TCAP of the remote end or by the near end TCAP.SSAPHSOC.M198B4C12nkhlrsubbh
SSAP_OC_SHORT_TERM_DENIALACCUMULATIONINT8Shows the number of SSAP operations rejected because of ShortTermDenial during the measurement period.The request to activate CCBS or CCNR has been rejected but the activation might be possible later.SSAPHSOC.M198B4C8nkhlrsubbh
SSAP_OC_STARTEDACCUMULATIONINT8Shows the number of started SSAP operations during the measurement period.SSAPHSOC.M198B4C1nkhlrsubbh
SSAP_OC_UNKNOWN_CAUSEACCUMULATIONINT8Shows the number of SSAP operations resulted in an error by unknown cause during the measurement period.SSAPHSOC.M198B4C6nkhlrsubbh
SSAP_OC_UNKNOWN_ERRORACCUMULATIONINT8Shows the number of SSAP operations resulted in an unknown error during the measurement period.SSAPHSOC.M198B4C10nkhlrsubbh


HLR_SSAP_Provider_Abort Performance Indicators

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


HLR_SSAP_Provider_Abort.Nokia.GSM.Session

Session Provider Abort counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_PA_NUMBERACCUMULATIONINT8Shows the number of TCAP provider aborts during the measurement period.SSAPHSPA.M198B7C1nkhlrsubbh


HLR_TCAP_Provider_Abort Performance Indicators

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


HLR_TCAP_Provider_Abort.Nokia.GSM.Session

INAP session provider aborts

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IAC_PA_NUMBERACCUMULATIONINT8Shows the number of TCAP provider aborts during the measurement period.IACIHDPA.M196B4C1 or IACIHSPA.M196B4C1nkhlrsubbh
INAP_OAC_PA_NUMBERACCUMULATIONINT8Shows the number of TCAP provider aborts during the measurement period.IACOHDPA.M197B4C1 or IACOHSPA.M196B4C1nkhlrsubbh


Interface_LAN Performance Indicators

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


Interface_LAN.Nokia.GSM.LAN_EMB

LAN Ethernet Message Bus counters

The performance data measurements for this KPI group are recorded against the combination of Interface_LAN and Transdir (transdir_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
LANEMB_LOAD_RATEINTENSITYINT8Average load rate.MLANEMBT.M293B2C2nklanpkbh
LANEMB_PEAK_RATEINTENSITYINT8Highest peak load rate.MLANEMBT.M293B2C3nklanpkbh
LANEMB_PEAK_TIME_IN_SECINTENSITYINT8The time of the highest peak load rate, the time of day in ASCII and seconds from the report start time in XML.MLANEMBT.M293B2C4nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Switch_Error

LAN switch errors

KPITypeData TypeDescriptionDerivationAdditional Summaries
COLLISIONSACCUMULATIONINT8Shows the collisions (tx_late_collisions + aborted_transmissions).CLANSEIF.M291B2C2 or HLANSEIF.M291B2C2 or MLANSEIF.M291B2C2nklanpkbh
CRC_ALIGN_ERRORSACCUMULATIONINT8Shows CRC Align Errors (crc_errors + frame_alignment).CLANSEIF.M291B2C3 or HLANSEIF.M291B2C3 or MLANSEIF.M291B2C3nklanpkbh
FIFO_OVERRUNACCUMULATIONINT8FIFO overrun count.CLANSEIF.M291B2C6 or HLANSEIF.M291B2C6 or MLANSEIF.M291B2C6nklanpkbh
LINE_NOT_READYACCUMULATIONINT8Line not ready counter.CLANSEIF.M291B2C7 or HLANSEIF.M291B2C7 or MLANSEIF.M291B2C7nklanpkbh
OVERSIZE_PACKETSACCUMULATIONINT8Packets are discarded because they are longer than maximum size.CLANSEIF.M291B2C5 or HLANSEIF.M291B2C5 or MLANSEIF.M291B2C5nklanpkbh
RECEIVED_PAUSE_OFF_PACKETSACCUMULATIONINT8Shows how many PAUSE OFF packets were received.CLANSEIF.M291B2C10 or HLANSEIF.M291B2C10 or MLANSEIF.M291B2C10nklanpkbh
RECEIVED_PAUSE_ON_PACKETSACCUMULATIONINT8Shows how many PAUSE ON packets were received.CLANSEIF.M291B2C9 or HLANSEIF.M291B2C9 or MLANSEIF.M291B2C9nklanpkbh
TRANSMITTED_PAUSE_OFF_PACKETSACCUMULATIONINT8Shows how many PAUSE OFF packets were transmitted.CLANSEIF.M291B2C12 or HLANSEIF.M291B2C12 or MLANSEIF.M291B2C12nklanpkbh
TRANSMITTED_PAUSE_ON_PACKETSACCUMULATIONINT8Shows how many PAUSE ON packets were transmitted.CLANSEIF.M291B2C11 or HLANSEIF.M291B2C11 or MLANSEIF.M291B2C11nklanpkbh
UNDERSIZE_PACKETSACCUMULATIONINT8Shows that packets are discarded because they are shorter than the minimum size (in Ethernet minimum sizeis 60 bytes).CLANSEIF.M291B2C4 or HLANSEIF.M291B2C4 or MLANSEIF.M291B2C4nklanpkbh
UNKNOWN_SAP_PACKETSACCUMULATIONINT8Shows unknown SAP packets.CLANSEIF.M291B2C8 or HLANSEIF.M291B2C8 or MLANSEIF.M291B2C8nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Switch_Received_Traffic

LAN Switch unit traffic

KPITypeData TypeDescriptionDerivationAdditional Summaries
RECEIVED_AVG_UTIL_RATEINTENSITYINT8Shows the average load rate of receiving interface.CLANSTIF.M288B2C28 or HLANSTIF.M288B2C28 or MLANSTIF.M288B2C28nklanpkbh
RECEIVED_BROADCAST_PACKETSACCUMULATIONINT8Shows the number of received broadcast packets.CLANSTIF.M288B2C12 or HLANSTIF.M288B2C12 or MLANSTIF.M288B2C12nklanpkbh
RECEIVED_MULTI_PACKETSACCUMULATIONINT8Shows the number of received multicats packets.CLANSTIF.M288B2C13 or HLANSTIF.M288B2C13 or MLANSTIF.M288B2C13nklanpkbh
RECEIVED_OCTETSACCUMULATIONINT8Shows the total number of received octets.CLANSTIF.M288B2C11 or HLANSTIF.M288B2C11 or MLANSTIF.M288B2C11nklanpkbh
RECEIVED_PACKETS_1024_1518ACCUMULATIONINT8Shows the total number of packets received and classified based on packet size (1024 < 1518).CLANSTIF.M288B2C25 or HLANSTIF.M288B2C25 or MLANSTIF.M288B2C25nklanpkbh
RECEIVED_PACKETS_128_255ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (128 < 255).CLANSTIF.M288B2C22 or HLANSTIF.M288B2C22 or MLANSTIF.M288B2C22nklanpkbh
RECEIVED_PACKETS_256_511ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (256 < 511).CLANSTIF.M288B2C23 or HLANSTIF.M288B2C23 or MLANSTIF.M288B2C23nklanpkbh
RECEIVED_PACKETS_512_1023ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (512 < 1023).CLANSTIF.M288B2C24 or HLANSTIF.M288B2C24 or MLANSTIF.M288B2C24nklanpkbh
RECEIVED_PACKETS_64ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (<64).CLANSTIF.M288B2C20 or HLANSTIF.M288B2C20 or MLANSTIF.M288B2C20nklanpkbh
RECEIVED_PACKETS_65_127ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (65<127).CLANSTIF.M288B2C21 or HLANSTIF.M288B2C21 or MLANSTIF.M288B2C21nklanpkbh
RECEIVED_PACKETSACCUMULATIONINT8Shows the total number of received packets.CLANSTIF.M288B2C10 or HLANSTIF.M288B2C10 or MLANSTIF.M288B2C10nklanpkbh
RECEIVED_PEAK_UTIL_RATEINTENSITYINT8Shows the highest peak load rate of receiving interface in five minutes period.CLANSTIF.M288B2C29 or HLANSTIF.M288B2C29 or MLANSTIF.M288B2C29nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Switch_Transmit_Traffic

LAN Switch unit transmit traffic

KPITypeData TypeDescriptionDerivationAdditional Summaries
TRANSMITTED_AVG_UTIL_RATEINTENSITYINT8Shows the average load rate of transmitting interface.CLANSTIF.M288B2C26 or HLANSTIF.M288B2C26 or MLANSTIF.M288B2C26nklanpkbh
TRANSMITTED_BROADCAST_PACKETSACCUMULATIONINT8Shows the number of transmitted broadcast packets.CLANSTIF.M288B2C8 or HLANSTIF.M288B2C8 or MLANSTIF.M288B2C8nklanpkbh
TRANSMITTED_MULTI_PACKETSACCUMULATIONINT8Shows the number of transmitted multicats packets.CLANSTIF.M288B2C9 or HLANSTIF.M288B2C9 or MLANSTIF.M288B2C9nklanpkbh
TRANSMITTED_OCTETSACCUMULATIONINT8Shows the total number of transmitted octets.CLANSTIF.M288B2C7 or HLANSTIF.M288B2C7 or MLANSTIF.M288B2C7nklanpkbh
TRANSMITTED_PACKETS_1024_1518ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (1024 < 1518).CLANSTIF.M288B2C19 or HLANSTIF.M288B2C19 or MLANSTIF.M288B2C19nklanpkbh
TRANSMITTED_PACKETS_128_255ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (128 < 255).CLANSTIF.M288B2C16 or HLANSTIF.M288B2C16 or MLANSTIF.M288B2C16nklanpkbh
TRANSMITTED_PACKETS_256_511ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (256 < 511).CLANSTIF.M288B2C17 or HLANSTIF.M288B2C17 or MLANSTIF.M288B2C17nklanpkbh
TRANSMITTED_PACKETS_512_1023ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (512 < 1023).CLANSTIF.M288B2C18 or HLANSTIF.M288B2C18 or MLANSTIF.M288B2C18nklanpkbh
TRANSMITTED_PACKETS_64ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (<64).CLANSTIF.M288B2C14 or HLANSTIF.M288B2C14 or MLANSTIF.M288B2C14nklanpkbh
TRANSMITTED_PACKETS_65_127ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (65 < 127).CLANSTIF.M288B2C15 or HLANSTIF.M288B2C15 or MLANSTIF.M288B2C15nklanpkbh
TRANSMITTED_PACKETSACCUMULATIONINT8Shows the total number of transmitted packets.CLANSTIF.M288B2C6 or HLANSTIF.M288B2C6 or MLANSTIF.M288B2C6nklanpkbh
TRANSMITTED_PEAK_UTIL_RATEINTENSITYINT8Shows the highest peak load rate of transmitting interface in five minutes period.CLANSTIF.M288B2C27 or HLANSTIF.M288B2C27 or MLANSTIF.M288B2C27nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Switch_Util

LAN Switch Utilisation

KPITypeData TypeDescriptionDerivationAdditional Summaries
IF_STATUSACCUMULATIONINT8Shows the state of LAN interface.CLANSTIF.M288B2C5 or HLANSTIF.M288B2C5 or MLANSTIF.M288B2C5nklanpkbh
LINK_DOWN_FAILUREACCUMULATIONINT8Shows Link down -failure during the measurement. Field is shown only if Linkdown -failure occurs. The counter is printed with value 1.CLANSTIF.M288B3C7 or HLANSTIF.M288B3C7 or MLANSTIF.M288B3C7nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Unit_Error

LAN Host Unit errors

KPITypeData TypeDescriptionDerivationAdditional Summaries
COLLISIONSACCUMULATIONINT8Shows the collisions (tx_late_collisions + aborted_transmissions).CLANHUEI.M292B2C2 or HLANHUEI.M292B2C2 or MLANHUEI.M292B2C2nklanpkbh
CRC_ALIGN_ERRORSACCUMULATIONINT8Shows CRC Align Errors (crc_errors + frame_alignment).CLANHUEI.M292B2C3 or HLANHUEI.M292B2C3 or MLANHUEI.M292B2C3nklanpkbh
FIFO_OVERRUNACCUMULATIONINT8FIFO overrun count.CLANHUEI.M292B2C6 or HLANHUEI.M292B2C6 or MLANHUEI.M292B2C6nklanpkbh
LINE_NOT_READYINTENSITYINT8Line not ready counter.CLANHUEI.M292B2C7 or HLANHUEI.M292B2C7 or MLANHUEI.M292B2C7nklanpkbh
OVERSIZE_PACKETSACCUMULATIONINT8Packets are discarded because they are longer than maximum size.CLANHUEI.M292B2C5 or HLANHUEI.M292B2C5 or MLANHUEI.M292B2C5nklanpkbh
RECEIVED_PAUSE_OFF_PACKETSACCUMULATIONINT8Shows how many PAUSE OFF packets were received.CLANHUEI.M292B2C10 or HLANHUEI.M292B2C10 or MLANHUEI.M292B2C10nklanpkbh
RECEIVED_PAUSE_ON_PACKETSACCUMULATIONINT8Shows how many PAUSE ON packets were received.CLANHUEI.M292B2C9 or HLANHUEI.M292B2C9 or MLANHUEI.M292B2C9nklanpkbh
TRANSMITTED_PAUSE_OFF_PACKETSACCUMULATIONINT8Shows how many PAUSE OFF packets were transmitted.CLANHUEI.M292B2C12 or HLANHUEI.M292B2C12 or MLANHUEI.M292B2C12nklanpkbh
TRANSMITTED_PAUSE_ON_PACKETSACCUMULATIONINT8Shows how many PAUSE ON packets were transmitted.CLANHUEI.M292B2C11 or HLANHUEI.M292B2C11 or MLANHUEI.M292B2C11nklanpkbh
UNDERSIZE_PACKETSACCUMULATIONINT8Shows that packets are discarded because they are shorter than the minimum size (in Ethernet minimum sizeis 60 bytes).CLANHUEI.M292B2C4 or HLANHUEI.M292B2C4 or MLANHUEI.M292B2C4nklanpkbh
UNKNOWN_SAP_PACKETSACCUMULATIONINT8Shows unknown SAP packets.CLANHUEI.M292B2C8 or HLANHUEI.M292B2C8 or MLANHUEI.M292B2C8nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic

LAN Host Unit received traffic counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
RECEIVED_AVG_UTIL_RATEINTENSITYINT8Shows the average load rate of receiving interface.CLANHUTI.M289B2C28 or HLANHUTI.M289B2C28 or MLANHUTI.M289B2C28nklanpkbh
RECEIVED_BROADCAST_PACKETSACCUMULATIONINT8Shows the number of received broadcast packets.CLANHUTI.M289B2C12 or HLANHUTI.M289B2C12 or MLANHUTI.M289B2C12nklanpkbh
RECEIVED_MULTI_PACKETSACCUMULATIONINT8Shows the number of received multicats packets.CLANHUTI.M289B2C13 or HLANHUTI.M289B2C13 or MLANHUTI.M289B2C13nklanpkbh
RECEIVED_OCTETSACCUMULATIONINT8Shows the total number of received octets.CLANHUTI.M289B2C11 or HLANHUTI.M289B2C11 or MLANHUTI.M289B2C11nklanpkbh
RECEIVED_PACKETS_1024_1518ACCUMULATIONINT8Shows the total number of packets received and classified based on packet size (1024 < 1518).CLANHUTI.M289B2C25 or HLANHUTI.M289B2C25 or MLANHUTI.M289B2C25nklanpkbh
RECEIVED_PACKETS_128_255ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (128 < 255).CLANHUTI.M289B2C22 or HLANHUTI.M289B2C22 or MLANHUTI.M289B2C22nklanpkbh
RECEIVED_PACKETS_256_511ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (256 < 511).CLANHUTI.M289B2C23 or HLANHUTI.M289B2C23 or MLANHUTI.M289B2C23nklanpkbh
RECEIVED_PACKETS_512_1023ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (512 < 1023).CLANHUTI.M289B2C24 or HLANHUTI.M289B2C24 or MLANHUTI.M289B2C24nklanpkbh
RECEIVED_PACKETS_64ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (<64).CLANHUTI.M289B2C20 or HLANHUTI.M289B2C20 or MLANHUTI.M289B2C20nklanpkbh
RECEIVED_PACKETS_65_127ACCUMULATIONINT8Shows the total number of received packets classified, based on packet size (65<127).CLANHUTI.M289B2C21 or HLANHUTI.M289B2C21 or MLANHUTI.M289B2C21nklanpkbh
RECEIVED_PACKETSACCUMULATIONINT8Shows the total number of received packets.CLANHUTI.M289B2C10 or HLANHUTI.M289B2C10 or MLANHUTI.M289B2C10nklanpkbh
RECEIVED_PEAK_UTIL_RATEINTENSITYINT8Shows the highest peak load rate of receiving interface in five minutes period.CLANHUTI.M289B2C29 or HLANHUTI.M289B2C29 or MLANHUTI.M289B2C29nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic

LAN Host unit transmit traffic

KPITypeData TypeDescriptionDerivationAdditional Summaries
TRANSMITTED_AVG_UTIL_RATEINTENSITYINT8Shows the average load rate of transmitting interface.CLANHUTI.M289B2C26 or HLANHUTI.M289B2C26 or MLANHUTI.M289B2C26nklanpkbh
TRANSMITTED_BROADCAST_PACKETSACCUMULATIONINT8Shows the number of transmitted broadcast packets.CLANHUTI.M289B2C8 or HLANHUTI.M289B2C8 or MLANHUTI.M289B2C8nklanpkbh
TRANSMITTED_MULTI_PACKETSACCUMULATIONINT8Shows the number of transmitted multicats packets.CLANHUTI.M289B2C9 or HLANHUTI.M289B2C9 or MLANHUTI.M289B2C9nklanpkbh
TRANSMITTED_OCTETSACCUMULATIONINT8Shows the total number of transmitted octets.CLANHUTI.M289B2C7 or HLANHUTI.M289B2C7 or MLANHUTI.M289B2C7nklanpkbh
TRANSMITTED_PACKETS_1024_1518ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (1024 < 1518).CLANHUTI.M289B2C19 or HLANHUTI.M289B2C19 or MLANHUTI.M289B2C19nklanpkbh
TRANSMITTED_PACKETS_128_255ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (128 < 255).CLANHUTI.M289B2C16 or HLANHUTI.M289B2C16 or MLANHUTI.M289B2C16nklanpkbh
TRANSMITTED_PACKETS_256_511ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (256 < 511).CLANHUTI.M289B2C17 or HLANHUTI.M289B2C17 or MLANHUTI.M289B2C17nklanpkbh
TRANSMITTED_PACKETS_512_1023ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (512 < 1023).CLANHUTI.M289B2C18 or HLANHUTI.M289B2C18 or MLANHUTI.M289B2C18nklanpkbh
TRANSMITTED_PACKETS_64ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (<64).CLANHUTI.M289B2C14 or HLANHUTI.M289B2C14 or MLANHUTI.M289B2C14nklanpkbh
TRANSMITTED_PACKETS_65_127ACCUMULATIONINT8Shows the total number of packets transmitted classified based on packet size (65 < 127).CLANHUTI.M289B2C15 or HLANHUTI.M289B2C15 or MLANHUTI.M289B2C15nklanpkbh
TRANSMITTED_PACKETSACCUMULATIONINT8Shows the total number of transmitted packets.CLANHUTI.M289B2C6 or HLANHUTI.M289B2C6 or MLANHUTI.M289B2C6nklanpkbh
TRANSMITTED_PEAK_UTIL_RATEINTENSITYINT8Shows the highest peak load rate of transmitting interface in five minutes period.CLANHUTI.M289B2C27 or HLANHUTI.M289B2C27 or MLANHUTI.M289B2C27nklanpkbh


Interface_LAN.Nokia.GSM.LAN_Unit_Utilisation

LAN Host unit utilisation

KPITypeData TypeDescriptionDerivationAdditional Summaries
IF_STATUSINTENSITYINT8Shows the state of LAN interface.CLANHUTI.M289B2C5 or HLANHUTI.M289B2C5 or MLANHUTI.M289B2C5nklanpkbh
LINK_DOWN_FAILUREINTENSITYINT8Shows Link down -failure during the measurement. Field is shown only if Linkdown -failure occurs. The counter is printed with value 1.CLANHUTI.M289B3C7 or HLANHUTI.M289B3C7 or MLANHUTI.M289B3C7nklanpkbh
TOTAL_TX_AND_RX_PACKETSACCUMULATIONINT8Total number of packets transmitted and receivedCLANHUTI.M289B2C10 + M289B2C6 or HLANHUTI.M289B2C10 + M289B2C6 or MLANHUTI.M289B2C10 + M289B2C6nklanpkbh


Interface_MAP Performance Indicators

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


Interface_MAP.Nokia.GSM.Data_Reliability

Indicates the reliability of data received

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_I_AC_UA_PA_DATA_PROV_RESTACCUMULATIONFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B5C1 or MAPHNETI.M192B5C1 or MAPHSN.M192B5C1 or MAPMDEST.M192B5C1 or MAPMNETI.M192B5C1 or MAPMSN.M192B5C1nkimapopbh
MAP_I_EC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.MAPHDEST.M192B13C1 or MAPHNETI.M192B13C1 or MAPHSN.M192B13C1 or MAPMDEST.M192B13C1 or MAPMNETI.M192B13C1 or MAPMSN.M192B13C1nkimapopbh
MAP_I_RC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B15C1 or MAPHNETI.M192B15C1 or MAPHSN.M192B15C1 or MAPMDEST.M192B15C1 or MAPMNETI.M192B15C1 or MAPMSN.M192B15C1nkimapopbh
MAP_O_AC_UA_PA_DATA_PROV_RESTACCUMULATIONINT8Shows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B2C1 or MAPHNETI.M192B2C1 or MAPHSN.M192B2C1 or MAPMDEST.M192B2C1 or MAPMNETI.M192B2C1 or MAPMSN.M192B2C1nkimapopbh
MAP_O_EC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B12C1 or MAPHNETI.M192B12C1 or MAPHSN.M192B12C1 or MAPMDEST.M192B12C1 or MAPMNETI.M192B12C1 or MAPMSN.M192B12C1nkimapopbh
MAP_O_RC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B14C1 or MAPHNETI.M192B14C1 or MAPHSN.M192B14C1 or MAPMDEST.M192B14C1 or MAPMNETI.M192B14C1 or MAPMSN.M192B14C1nkimapopbh


Interface_MAP.Nokia.GSM.Incoming_App_Context_Part1

Incoming Application Context Part 1

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_I_AC_1_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.MAPHDEST.M192B3C1 or MAPHNETI.M192B3C1 or MAPHSN.M192B3C1 or MAPMDEST.M192B3C1 or MAPMNETI.M192B3C1 or MAPMSN.M192B3C1nkimapopbh
MAP_I_AC_1_SUM_FAILED_ACSACCUMULATIONINT8Shows the total number of failed incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B3C5 or MAPHNETI.M192B3C5 or MAPHSN.M192B3C5 or MAPMDEST.M192B3C5 or MAPMNETI.M192B3C5 or MAPMSN.M192B3C5nkimapopbh
MAP_I_AC_1_SUM_STARTED_ACSACCUMULATIONINT8Shows the total number of started incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B3C3 or MAPHNETI.M192B3C3 or MAPHSN.M192B3C3 or MAPMDEST.M192B3C3 or MAPMNETI.M192B3C3 or MAPMSN.M192B3C3nkimapopbh
MAP_I_AC_1_SUM_SUCCEEDED_ACSACCUMULATIONINT8Shows the total number of succeeded incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B3C4 or MAPHNETI.M192B3C4 or MAPHSN.M192B3C4 or MAPMDEST.M192B3C4 or MAPMNETI.M192B3C4 or MAPMSN.M192B3C4nkimapopbh


Interface_MAP.Nokia.GSM.Incoming_App_Context_Part2

Incoming Application Context report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_I_AC_2_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.MAPHDEST.M192B4C1 or MAPHNETI.M192B4C1 or MAPHSN.M192B4C1 or MAPMDEST.M192B4C1 or MAPMNETI.M192B4C1 or MAPMSN.M192B4C1nkimapopbh
MAP_I_AC_2_SUM_FAILED_ACSACCUMULATIONINT8Shows the total number of failed incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B4C5 or MAPHNETI.M192B4C5 or MAPHSN.M192B4C5 or MAPMDEST.M192B4C5 or MAPMNETI.M192B4C5 or MAPMSN.M192B4C5nkimapopbh
MAP_I_AC_2_SUM_STARTED_ACSACCUMULATIONINT8Shows the total number of started incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B4C3 or MAPHNETI.M192B4C3 or MAPHSN.M192B4C3 or MAPMDEST.M192B4C3 or MAPMNETI.M192B4C3 or MAPMSN.M192B4C3nkimapopbh
MAP_I_AC_2_SUM_SUCCEEDED_ACSACCUMULATIONINT8Shows the total number of succeeded incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B4C4 or MAPHNETI.M192B4C4 or MAPHSN.M192B4C4 or MAPMDEST.M192B4C4 or MAPMNETI.M192B4C4 or MAPMSN.M192B4C4nkimapopbh


Interface_MAP.Nokia.GSM.Incoming_App_Context_Part3

MAP Incoming Application Context report part 3

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_I_AC_3_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.MAPHDEST.M192B7C1 or MAPHNETI.M192B7C1 or MAPHSN.M192B7C1 or MAPMDEST.M192B7C1 or MAPMNETI.M192B7C1 or MAPMSN.M192B7C1nkimapopbh
MAP_I_AC_3_SUM_FAILED_ACSACCUMULATIONINT8Shows the total number of failed incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B7C5 or MAPHNETI.M192B7C5 or MAPHSN.M192B7C5 or MAPMDEST.M192B7C5 or MAPMNETI.M192B7C5 or MAPMSN.M192B7C5nkimapopbh
MAP_I_AC_3_SUM_STARTED_ACSACCUMULATIONINT8Shows the total number of started incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B7C3 or MAPHNETI.M192B7C3 or MAPHSN.M192B7C3 or MAPMDEST.M192B7C3 or MAPMNETI.M192B7C3 or MAPMSN.M192B7C3nkimapopbh
MAP_I_AC_3_SUM_SUCCEEDED_ACSACCUMULATIONINT8Shows the total number of succeeded incoming MAP application contexts in the report part during the measurement period.MAPHDEST.M192B7C4 or MAPHNETI.M192B7C4 or MAPHSN.M192B7C4 or MAPMDEST.M192B7C4 or MAPMNETI.M192B7C4 or MAPMSN.M192B7C4nkimapopbh


Interface_MAP.Nokia.GSM.Incoming_Operation_Part1

MAP Incoming Application context report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_I_OC_1_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.MAPHDEST.M192B10C1 or MAPHNETI.M192B10C1 or MAPHSN.M192B10C1 or MAPMDEST.M192B10C1 or MAPMNETI.M192B10C1 or MAPMSN.M192B10C1nkimapopbh
MAP_I_OC_1_SUM_FAILED_OCSACCUMULATIONINT8Shows the total number of failed incoming MAP operations in the report part during the measurement period.MAPHDEST.M192B10C5 or MAPHNETI.M192B10C5 or MAPHSN.M192B10C5 or MAPMDEST.M192B10C5 or MAPMNETI.M192B10C5 or MAPMSN.M192B10C5nkimapopbh
MAP_I_OC_1_SUM_STARTED_OCSACCUMULATIONINT8Shows the total number of started incoming MAP operations in the report part during the measurement period.MAPHDEST.M192B10C3 or MAPHNETI.M192B10C3 or MAPHSN.M192B10C3 or MAPMDEST.M192B10C3 or MAPMNETI.M192B10C3 or MAPMSN.M192B10C3nkimapopbh
MAP_I_OC_1_SUM_SUCCEEDED_OCSACCUMULATIONINT8Shows the total number of succeeded incoming MAP operations in the report part during the measurement period.MAPHDEST.M192B10C4 or MAPHNETI.M192B10C4 or MAPHSN.M192B10C4 or MAPMDEST.M192B10C4 or MAPMNETI.M192B10C4 or MAPMSN.M192B10C4nkimapopbh


Interface_MAP.Nokia.GSM.Incoming_Operation_Part2

MAP Incoming Operations report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_MAP_I_OC_2_SUCCEEDED_OCSPERCENTAGEFLOATShows the percentage of successful incoming MAP operations in the report part during the measurement period.percentok(({Interface_MAP.Nokia.GSM.Incoming_Operation_Part1.MAP_I_OC_1_SUM_SUCCEEDED_OCS} + {MAP_I_OC_2_SUM_SUCCEEDED_OCS}), ({Interface_MAP.Nokia.GSM.Incoming_Operation_Part1.MAP_I_OC_1_SUM_STARTED_OCS} + {MAP_I_OC_2_SUM_STARTED_OCS}))nkimapopbh
MAP_I_OC_2_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.MAPHDEST.M192B11C1 or MAPHNETI.M192B11C1 or MAPHSN.M192B11C1 or MAPMDEST.M192B11C1 or MAPMNETI.M192B11C1 or MAPMSN.M192B11C1nkimapopbh
MAP_I_OC_2_SUM_FAILED_OCSACCUMULATIONINT8Shows the total number of failed incoming MAP operations in the report part during the measurement period.MAPHDEST.M192B11C5 or MAPHNETI.M192B11C5 or MAPHSN.M192B11C5 or MAPMDEST.M192B11C5 or MAPMNETI.M192B11C5 or MAPMSN.M192B11C5nkimapopbh
MAP_I_OC_2_SUM_STARTED_OCSACCUMULATIONINT8Shows the total number of started incoming MAP operations in the report part during the measurement period.MAPHDEST.M192B11C3 or MAPHNETI.M192B11C3 or MAPHSN.M192B11C3 or MAPMDEST.M192B11C3 or MAPMNETI.M192B11C3 or MAPMSN.M192B11C3nkimapopbh
MAP_I_OC_2_SUM_SUCCEEDED_OCSACCUMULATIONINT8Shows the total number of succeeded incoming MAP operations in the report part during the measurement period.MAPHDEST.M192B11C4 or MAPHNETI.M192B11C4 or MAPHSN.M192B11C4 or MAPMDEST.M192B11C4 or MAPMNETI.M192B11C4 or MAPMSN.M192B11C4nkimapopbh


Interface_MAP.Nokia.GSM.MAP_Reject

MAP rejects

The performance data measurements for this KPI group are recorded against the combination of Interface_MAP and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_RC_REJECTACCUMULATIONINT8Shows the number of rejected operations in the report part during the measurement period.MAPHDTRC.M192B21C1 or MAPHNIRC.M192B21C1 or MAPHSNRC.M192B21C1 or MAPMDTRC.M192B21C1 or MAPMNIRC.M192B21C1 or MAPMSNRC.M192B21C1nkimapopbh


Interface_MAP.Nokia.GSM.Outgoing_App_Context_Part1

MAP Outgoing Application context report part1

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_O_AC_1_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B0C1 or MAPHNETI.M192B0C1 or MAPHSN.M192B0C1 or MAPMDEST.M192B0C1 or MAPMNETI.M192B0C1 or MAPMSN.M192B0C1nkimapopbh
MAP_O_AC_1_SUM_FAILED_ACSACCUMULATIONINT8Shows the total number of failed outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B0C5 or MAPHNETI.M192B0C5 or MAPHSN.M192B0C5 or MAPMDEST.M192B0C5 or MAPMNETI.M192B0C5 or MAPMSN.M192B0C5nkimapopbh
MAP_O_AC_1_SUM_STARTED_ACSACCUMULATIONINT8Shows the total number of started outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B0C3 or MAPHNETI.M192B0C3 or MAPHSN.M192B0C3 or MAPMDEST.M192B0C3 or MAPMNETI.M192B0C3 or MAPMSN.M192B0C3nkimapopbh
MAP_O_AC_1_SUM_SUCCEEDED_ACSACCUMULATIONINT8Shows the total number of succeeded outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B0C4 or MAPHNETI.M192B0C4 or MAPHSN.M192B0C4 or MAPMDEST.M192B0C4 or MAPMNETI.M192B0C4 or MAPMSN.M192B0C4nkimapopbh


Interface_MAP.Nokia.GSM.Outgoing_App_Context_Part2

MAP Outgoing Application context part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_O_AC_2_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B1C1 or MAPHNETI.M192B1C1 or MAPHSN.M192B1C1 or MAPMDEST.M192B1C1 or MAPMNETI.M192B1C1 or MAPMSN.M192B1C1nkimapopbh
MAP_O_AC_2_SUM_FAILED_ACSACCUMULATIONINT8Shows the total number of failed outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B1C5 or MAPHNETI.M192B1C5 or MAPHSN.M192B1C5 or MAPMDEST.M192B1C5 or MAPMNETI.M192B1C5 or MAPMSN.M192B1C5nkimapopbh
MAP_O_AC_2_SUM_STARTED_ACSACCUMULATIONFLOATShows the total number of started outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B1C3 or MAPHNETI.M192B1C3 or MAPHSN.M192B1C3 or MAPMDEST.M192B1C3 or MAPMNETI.M192B1C3 or MAPMSN.M192B1C3nkimapopbh
MAP_O_AC_2_SUM_SUCCEEDED_ACSACCUMULATIONINT8Shows the total number of succeeded outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B1C4 or MAPHNETI.M192B1C4 or MAPHSN.M192B1C4 or MAPMDEST.M192B1C4 or MAPMNETI.M192B1C4 or MAPMSN.M192B1C4nkimapopbh


Interface_MAP.Nokia.GSM.Outgoing_App_Context_Part3

MAP Outgoing Application Context report part 3

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_O_AC_3_DATA_PROV_RESTARTINTENSITYINT8Shows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B6C1 or MAPHNETI.M192B6C1 or MAPHSN.M192B6C1 or MAPMDEST.M192B6C1 or MAPMNETI.M192B6C1 or MAPMSN.M192B6C1nkimapopbh
MAP_O_AC_3_SUM_FAILED_ACSACCUMULATIONINT8Shows the total number of failed outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B6C5 or MAPHNETI.M192B6C5 or MAPHSN.M192B6C5 or MAPMDEST.M192B6C5 or MAPMNETI.M192B6C5 or MAPMSN.M192B6C5nkimapopbh
MAP_O_AC_3_SUM_STARTED_ACSACCUMULATIONINT8Shows the total number of started outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B6C3 or MAPHNETI.M192B6C3 or MAPHSN.M192B6C3 or MAPMDEST.M192B6C3 or MAPMNETI.M192B6C3 or MAPMSN.M192B6C3nkimapopbh
MAP_O_AC_3_SUM_SUCCEEDED_ACSACCUMULATIONINT8Shows the total number of succeeded outgoing MAP application contexts in the report part during the measurement period.MAPHDEST.M192B6C4 or MAPHNETI.M192B6C4 or MAPHSN.M192B6C4 or MAPMDEST.M192B6C4 or MAPMNETI.M192B6C4 or MAPMSN.M192B6C4nkimapopbh


Interface_MAP.Nokia.GSM.Outgoing_Operation_Part1

MAP Outgoing Operations report part 1

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_O_OC_1_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B8C1 or MAPHNETI.M192B8C1 or MAPHSN.M192B8C1 or MAPMDEST.M192B8C1 or MAPMNETI.M192B8C1 or MAPMSN.M192B8C1nkimapopbh
MAP_O_OC_1_SUM_FAILED_OCSACCUMULATIONINT8Shows the total number of failed outgoing MAP operations in the report part during the measurement period.MAPHDEST.M192B8C5 or MAPHNETI.M192B8C5 or MAPHSN.M192B8C5 or MAPMDEST.M192B8C5 or MAPMNETI.M192B8C5 or MAPMSN.M192B8C5nkimapopbh
MAP_O_OC_1_SUM_STARTED_OCSACCUMULATIONINT8Shows the total number of started outgoing MAP operations in the report part during the measurement period.MAPHDEST.M192B8C3 or MAPHNETI.M192B8C3 or MAPHSN.M192B8C3 or MAPMDEST.M192B8C3 or MAPMNETI.M192B8C3 or MAPMSN.M192B8C3nkimapopbh
MAP_O_OC_1_SUM_SUCCEEDED_OCSACCUMULATIONINT8Shows the total number of succeeded outgoing MAP operations in the report part during the measurement period.MAPHDEST.M192B8C4 or MAPHNETI.M192B8C4 or MAPHSN.M192B8C4 or MAPMDEST.M192B8C4 or MAPMNETI.M192B8C4 or MAPMSN.M192B8C4nkimapopbh
MAP_TOTAL_I_O_STARTED_OCSACCUMULATIONINT8Shows the total number of started outgoing and incoming MAP operations during the measurement period.MAPHDEST.M192B8C3 + M192B9C3 + M192B10C3 + M192B11C3 or MAPHNETI.M192B8C3 + M192B9C3 + M192B10C3 + M192B11C3 or MAPHSN.M192B8C3 + M192B9C3 + M192B10C3 + M192B11C3 or MAPMDEST.M192B8C3 + M192B9C3 + M192B10C3 + M192B11C3 or MAPMNETI.M192B8C3 + M192B9C3 + M192B10C3 + M192B11C3 or MAPMSN.M192B8C3 + M192B9C3 + M192B10C3 + M192B11C3nkimapopbh


Interface_MAP.Nokia.GSM.Outgoing_Operation_Part2

MAP Outgoing operations report part2

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_MAP_O_OC_2_SUCCEEDED_OCSPERCENTAGEFLOATShows the percentage of successful outgoing MAP operations in the report part during the measurement period.percentok(({Interface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_O_OC_1_SUM_SUCCEEDED_OCS} + {MAP_O_OC_2_SUM_SUCCEEDED_OCS}), ({Interface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_O_OC_1_SUM_STARTED_OCS} + {MAP_O_OC_2_SUM_STARTED_OCS}))nkimapopbh
MAP_O_OC_2_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.MAPHDEST.M192B9C1 or MAPHNETI.M192B9C1 or MAPHSN.M192B9C1 or MAPMDEST.M192B9C1 or MAPMNETI.M192B9C1 or MAPMSN.M192B9C1nkimapopbh
MAP_O_OC_2_SUM_FAILED_OCSACCUMULATIONINT8Shows the total number of failed outgoing MAP operations in the report part during the measurement period.MAPHDEST.M192B9C5 or MAPHNETI.M192B9C5 or MAPHSN.M192B9C5 or MAPMDEST.M192B9C5 or MAPMNETI.M192B9C5 or MAPMSN.M192B9C5nkimapopbh
MAP_O_OC_2_SUM_STARTED_OCSACCUMULATIONINT8Shows the total number of started outgoing MAP operations in the report part during the measurement period.MAPHDEST.M192B9C3 or MAPHNETI.M192B9C3 or MAPHSN.M192B9C3 or MAPMDEST.M192B9C3 or MAPMNETI.M192B9C3 or MAPMSN.M192B9C3nkimapopbh
MAP_O_OC_2_SUM_SUCCEEDED_OCSACCUMULATIONINT8Shows the total number of succeeded outgoing MAP operations in the report part during the measurement period.MAPHDEST.M192B9C4 or MAPHNETI.M192B9C4 or MAPHSN.M192B9C4 or MAPMDEST.M192B9C4 or MAPMNETI.M192B9C4 or MAPMSN.M192B9C4nkimapopbh


LAC Performance Indicators

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


LAC.Nokia.GSM.Paging

This measurement provides the number of pagings (attempted and successful) in different location areas. It contains the Normal and Telemetric subscribers paging.

KPITypeData TypeDescriptionDerivationAdditional Summaries
answer_timeINTENSITYFLOATThe average time between the last paging request message and the corresponding paging response (during a paging) is shown in the ANS.TIME field in tenth of second. If there is not any successful paging this counter is not applicable.PPLAC.M353B3C7nkmtbh
datamissing_in_paging_per_laINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, only a subset of the data could be collected. It means that the printed counters per LAC are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)PPLAC.M353B2C1nkmtbh
paging_attempt_perlaACCUMULATIONINT8Number of initiated pagings from the VLR to the specific LA. This counter contains the paging of both Normal and telemetric subscribers.PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.PPLAC.M353B3C1nkmtbh
paging_attempt_with_imsifailACCUMULATIONINT8The number of paging attempt with IMSI for failed pagings (ATT#(FAIL)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging failed. This counter contains the paging of both Normal and telemetric subscribers. PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.PPLAC.M353B3C5nkmtbh
paging_attempt_with_imsisuccACCUMULATIONINT8The number of paging attempt with IMSI for successful pagings (ATT#(SUCC)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging was successful. This counter contains the paging of both Normal and telemetric subscribers. PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.PPLAC.M353B3C3nkmtbh
paging_attempt_with_tmsifailACCUMULATIONINT8The number of paging attempt with TMSI for failed pagings (ATT#(FAIL)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging failed. This counter contains the paging of both Normal and telemetric subscribers.PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.PPLAC.M353B3C6nkmtbh
paging_attempt_with_tmsisuccACCUMULATIONINT8The number of paging attempt with TMSI for successful pagings (ATT#(SUCC)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging was successful. This counter contains the paging of both Normal and telemetric subscribers.PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.PPLAC.M353B3C4nkmtbh
paging_succ_perlaACCUMULATIONINT8Number of successful pagings in VLR in the specific LA. This counter contains the paging of both Normal and telemetric subscribers. PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.PPLAC.M353B3C2nkmtbh
prevented_pagingACCUMULATIONINT8This counter indicates the number of pagings failed in the specific LA because of paging preventionPPLAC.M353B3C8nkmtbh


LAC.Nokia.GSM.Telemetrica_Subscribers

This section describes the counters of M78: MeO MSC / LAC.

KPITypeData TypeDescriptionDerivationAdditional Summaries
tm_subsc_category_1INTENSITYINTEGERThe number of telemetric subscriber category 1 in LA.VLRLAC.M78B3C3nkmtbh
tm_subsc_category_2INTENSITYINTEGERThe number of telemetric subscriber category 2 in LA.VLRLAC.M78B3C4nkmtbh
tm_subsc_category_3INTENSITYINTEGERThe number of telemetric subscriber category 3 in LA.VLRLAC.M78B3C5nkmtbh


LAC.Nokia.GSM.VLR_LAC

This measurement contains the location area specific part of the measurement results of the VLR measurement. It contains information about the number of subscribers in each location area.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ave_subsc_in_laINTENSITYINTEGERThe average number of subscribers in the location area during a measurement periodVLRNLAC.M80B2C4nkmtbh
subsc_in_laINTENSITYINTEGERThe number of subscribers in the location area at the end of a measurement periodVLRNLAC.M80B2C3nkmtbh


LAC_Access_Type Performance Indicators

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


LAC_Access_Type.Nokia.GSM.Location_Update

Location updates per LAC

KPITypeData TypeDescriptionDerivationAdditional Summaries
IE_VLR_LU_REROUTEACCUMULATIONINT8It indicates the number of rerouting events of the non-supporting UEs in a MOCN configuration during the Inter-VLR Location Update attempts. Measured object is MCC/MNC/LAC Draft Database Description for MSC M14.1 MeasurementsLULAC.M240B1C9nkmtbh
IMSI_ATTACH_ATTEMPTACCUMULATIONINT8Indicates the number of IMSI Attach attempts.LULAC.M240B1C7nkmtbh
IMSI_ATTACH_SUCCESSACCUMULATIONINT8Indicates the number of successful IMSI Attach events.LULAC.M240B1C8nkmtbh
INTER_VLR_LOC_UPDATE_ATTEMPTACCUMULATIONINT8Indicates the number of Inter-VLR Location Update attempts.Note that in case of SIP access type field contains '-' as this location update type does not make sense in that case.LULAC.M240B1C3nkmtbh
INTER_VLR_LOC_UPDATE_SUCCESSACCUMULATIONINT8Indicates the number of successful Inter-VLR Location Update events.Note that in case of SIP access type field contains '-' as this location update type does not make sense in that case.LULAC.M240B1C4nkmtbh
INTRA_VLR_LOC_UPDATE_ATTEMPTACCUMULATIONINT8Indicates the number of Intra-VLR Location Update attempts.Note that in case of SIP access type field contains '-' as this location update type does not make sense in that case.LULAC.M240B1C1nkmtbh
INTRA_VLR_LOC_UPDATE_SUCCESSACCUMULATIONINT8Indicates the number of successful Intra-VLR Location Update events.Note that in case of SIP access type field contains '-' as this location update type does not make sense in that case.LULAC.M240B1C2nkmtbh
PERIODIC_LOC_UPDATE_ATTEMPTACCUMULATIONINT8Indicates the number of Periodic Location Update attempts.LULAC.M240B1C5nkmtbh
PERIODIC_LOC_UPDATE_SUCCESSACCUMULATIONINT8Indicates the number of successful Periodic Location Update events.LULAC.M240B1C6nkmtbh


MAP_Application_Context Performance Indicators

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


MAP_Application_Context.Nokia.GSM.Session

MAP Application Context sessions

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_AC_CANCELLEDACCUMULATIONINT8Shows the number of interruptions caused by the expiration of TCAP time supervision in the report part during the measurement period.MAPHDTAC.M192B16C6 or MAPHNIAC.M192B16C6 or MAPHSNAC.M192B16C6 or MAPMDTAC.M192B16C6 or MAPMNIAC.M192B16C6 or MAPMSNAC.M192B16C6nkhlrsubbh, nkmtbh
MAP_AC_OWN_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the MAP itself in the report part during the measurement period.MAPHDTAC.M192B16C3 or MAPHNIAC.M192B16C3 or MAPHSNAC.M192B16C3 or MAPMDTAC.M192B16C3 or MAPMNIAC.M192B16C3 or MAPMSNAC.M192B16C3nkhlrsubbh, nkmtbh
MAP_AC_STARTEDACCUMULATIONINT8Shows the number of started MAP application contexts in the report part during the measurement period.MAPHDTAC.M192B16C1 or MAPHNIAC.M192B16C1 or MAPHSNAC.M192B16C1 or MAPMDTAC.M192B16C1 or MAPMNIAC.M192B16C1 or MAPMSNAC.M192B16C1nkhlrsubbh, nkmtbh
MAP_AC_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the TCAP in the MAP-S or in the MAP-R end in the report part, during the measurement period.MAPHDTAC.M192B16C5 or MAPHNIAC.M192B16C5 or MAPHSNAC.M192B16C5 or MAPMDTAC.M192B16C5 or MAPMNIAC.M192B16C5 or MAPMSNAC.M192B16C5nkhlrsubbh, nkmtbh
MAP_AC_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the receiving MAP (MAP-R) entity in the report part during the measurement period.MAPHDTAC.M192B16C4 or MAPHNIAC.M192B16C4 or MAPHSNAC.M192B16C4 or MAPMDTAC.M192B16C4 or MAPMNIAC.M192B16C4 or MAPMSNAC.M192B16C4nkhlrsubbh, nkmtbh
MAP_AC_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of interruptions caused by the expiration of MAP internal time supervision in the report part, during the measurement period.MAPHDTAC.M192B16C7 or MAPHNIAC.M192B16C7 or MAPHSNAC.M192B16C7 or MAPMDTAC.M192B16C7 or MAPMNIAC.M192B16C7 or MAPMSNAC.M192B16C7nkhlrsubbh, nkmtbh
MAP_AC_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by MAP user in the report part during the measurement period.MAPHDTAC.M192B16C2 or MAPHNIAC.M192B16C2 or MAPHSNAC.M192B16C2 or MAPMDTAC.M192B16C2 or MAPMNIAC.M192B16C2 or MAPMSNAC.M192B16C2nkhlrsubbh, nkmtbh
MAP_AC_VERSION_CHANGEACCUMULATIONINT8Shows the number of changes in used MAP version. This happens when MAP-R does not recognise or support a particular version and another version is taken into use.MAPHDTAC.M192B16C8 or MAPHNIAC.M192B16C8 or MAPHSNAC.M192B16C8 or MAPMDTAC.M192B16C8 or MAPMNIAC.M192B16C8 or MAPMSNAC.M192B16C8nkhlrsubbh, nkmtbh


MAP_Error_Code Performance Indicators

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


MAP_Error_Code.Nokia.GSM.Error

MAP Error codes

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_EC_ERRORACCUMULATIONINT8Shows the number of operations resulted in an error in the report part during the measurement period.MAPHDTEC.M192B20C1 or MAPHNIEC.M192B20C1 or MAPHSNEC.M192B20C1 or MAPMDTEC.M192B20C1 or MAPMNIEC.M192B20C1 or MAPMSNEC.M192B20C1nkhlrsubbh, nkmtbh


MAP_Operation_Code Performance Indicators

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


MAP_Operation_Code.Nokia.GSM.Operations

MAP Operations

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_OC_ABORTEDACCUMULATIONINT8Shows the number of aborted operations in the report part during the measurement period.MAPHDTOC.M192B19C5 or MAPHNIOC.M192B19C5 or MAPHSNOC.M192B19C5 or MAPMDTOC.M192B19C5 or MAPMNIOC.M192B19C5 or MAPMSNOC.M192B19C5nkhlrsubbh, nkmtbh
MAP_OC_CANCELLEDACCUMULATIONINT8Shows the number of operations terminated due to the expiration of time supervision in the report part during the measurement period.MAPHDTOC.M192B19C2 or MAPHNIOC.M192B19C2 or MAPHSNOC.M192B19C2 or MAPMDTOC.M192B19C2 or MAPMNIOC.M192B19C2 or MAPMSNOC.M192B19C2nkhlrsubbh, nkmtbh
MAP_OC_ERRORACCUMULATIONINT8Shows the number of MAP operations terminated by an error in the report part during the measurement period.MAPHDTOC.M192B19C3 or MAPHNIOC.M192B19C3 or MAPHSNOC.M192B19C3 or MAPMDTOC.M192B19C3 or MAPMNIOC.M192B19C3 or MAPMSNOC.M192B19C3nkhlrsubbh, nkmtbh
MAP_OC_REJECTEDACCUMULATIONINT8Shows the number of rejected operations in the report part during the measurement period.MAPHDTOC.M192B19C4 or MAPHNIOC.M192B19C4 or MAPHSNOC.M192B19C4 or MAPMDTOC.M192B19C4 or MAPMNIOC.M192B19C4 or MAPMSNOC.M192B19C4nkhlrsubbh, nkmtbh
MAP_OC_SUCCEEDEDACCUMULATIONINT8Shows the number of succeeded MAP operations in the report part during the measurement period.MAPHDTOC.M192B19C1 or MAPHNIOC.M192B19C1 or MAPHSNOC.M192B19C1 or MAPMDTOC.M192B19C1 or MAPMNIOC.M192B19C1 or MAPMSNOC.M192B19C1nkhlrsubbh, nkmtbh


MAP_Provider_Abort Performance Indicators

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


MAP_Provider_Abort.Nokia.GSM.Application_Context_Abort

MAP Application context aborts

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_UA_PA_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by TCAP in the MAP-S or MAP-R end in the report part during the measurement period.MAPHDTPA.M192B18C1 or MAPHNIPA.M192B18C1 or MAPHSNPA.M192B18C1 or MAPMDTPA.M192B18C1 or MAPMNIPA.M192B18C1 or MAPMSNPA.M192B18C1nkhlrsubbh, nkmtbh


MAP_User_Abort Performance Indicators

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


MAP_User_Abort.Nokia.GSM.Application_Context_Abort

MAP TCAP Application Context User Aborts

KPITypeData TypeDescriptionDerivationAdditional Summaries
MAP_UA_PA_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the receiving MAP (MAP-R) entity in the report part during the measurement period.MAPHDTUA.M192B17C1 or MAPHNIUA.M192B17C1 or MAPHSNUA.M192B17C1 or MAPMDTUA.M192B17C1 or MAPMNIUA.M192B17C1 or MAPMSNUA.M192B17C1nkhlrsubbh, nkmtbh


MGW Performance Indicators

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


MGW.Nokia.GSM.Circuit_Seizure_Supervision

Circuit seizure supervision measurement shows the circuits that have been free or reserved during the entire supervision period

KPITypeData TypeDescriptionDerivationAdditional Summaries
cise_state_0_free_ff_reserved2INTENSITYINTEGER(Obsolete in M13.5, CRCDS block now supported under TSL object) State of the circuit (PCM-TSL) during the supervision period. Possible values: FREE (0) = the circuit has been free the whole of the supervision period RESERVED (255) = the circuit has been reserved the whole of the supervision period. Those circuits under circuit seizure supervision whose state has changed during the supervision period are not listed in the report.obsolete.obsoletenkmgwhmbh


MGW.Nokia.GSM.Handover

The handover measurement shows the number of different types of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
from_neighbour_mgw_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring MGWNMGW.M345B1C4nkmgwhmbh
from_neighbour_mgw_okACCUMULATIONINT8Successful handovers from neighbouring MGWNMGW.M345B1C3nkmgwhmbh
otherlegacybscrncfromnokACCUMULATIONINT8Unsuccessful handovers from RNCs/BSCs which are not connected to MGW in same MSC (MGW index is not applicable in this case).NMGW.M345B2C4nkmgwhmbh
otherlegacybscrncfromokACCUMULATIONINT8Successful handovers from RNCs/BSCs which are not connected to MGW in same MSC.NMGW.M345B2C3nkmgwhmbh
otherlegacybscrnctonokACCUMULATIONINT8Unsuccessful handovers to RNCs/BSCs which are not connected to MGW in same MSC (MGW index is not applicable in this case).NMGW.M345B2C2nkmgwhmbh
otherlegacybscrnctookACCUMULATIONINT8Successful handovers to RNCs/BSCs which are not connected to MGW in same MSC.NMGW.M345B2C1nkmgwhmbh
othermgwintermssfromnokACCUMULATIONINT8Unsuccessful handovers from MGWs connected to other MSC (in incoming inter MSC handover case we do not know the old MGW index in MSC- B).NMGW.M345B2C9nkmgwhmbh
othermgwintermssfromokACCUMULATIONINT8Successful handovers from MGWs in other MSC.NMGW.M345B2C8nkmgwhmbh
othermgwintermsstonokACCUMULATIONINT8Unsuccessful handovers to MGWs connected to other MSC (in outgoing inter MSC handover case we do not know the new MGW index in MSC- A).NMGW.M345B2C7nkmgwhmbh
othermgwintermsstookACCUMULATIONINT8Successful handovers to MGWs in other MSC.NMGW.M345B2C6nkmgwhmbh
othermgwintramsstonokACCUMULATIONINT8Unsuccessful intra MSC handovers to MGWs when the MGW index is not known because the handover failed before or during the resource reservation.NMGW.M345B2C5nkmgwhmbh
toneighbourmgwnokACCUMULATIONINT8Unsuccessful handovers to neighbouring MGWNMGW.M345B1C2nkmgwhmbh
toneighbourmgwokACCUMULATIONINT8Successful handovers to neighbouring MGWNMGW.M345B1C1nkmgwhmbh


MGW.Nokia.GSM.IP_ATM_traffic

IP ATM traffic data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_successful_aal1_callsPERCENTAGEFLOATPercentage successful AAL1 callspercentok({aal1_success_calls}, {aal1_call_amount}) 
%_successful_aal2_callsPERCENTAGEFLOATPercentage successful AAL2 callspercentok({aal2_success_calls}, {aal2_call_amount}) 
%_successful_ip_callsPERCENTAGEFLOATPercentage successful IP callspercentok({ip_success_calls}, {ip_call_amount}) 
%_successful_ipv6_callsPERCENTAGEFLOATPercentage successful IPv6 callspercentok({ipv6_success_calls}, {ipv6_call_amount}) 
aal1_call_amountACCUMULATIONINT8The AAL1CALL AMOUNT counter shows the number of attempted interconnecting termination reservations for ATM AAL1 connections between MGWs.IPATM.M390B2C1 
aal1_congested_fcallsACCUMULATIONINT8The AAL1 CONGESTED FCALLS counter shows the number of termination reservation attempts for ATM AAL1 connections where the reservation failed due to congestion. The congestion is shown if it occurs in any of the MGWs.IPATM.M390B2C3 
aal1_failed_callsACCUMULATIONINT8The AAL1 FAILED CALLS counter shows the number of failed termination reservations for ATM AAL1 connections. This counter excludes reservations that failed due to congestion.IPATM.M390B2C4 
aal1_seiz_timeACCUMULATIONINT8The AAL1 ERLANGS counter shows the amount of AAL1 traffic between the media gateways in erlangs. That means the total reservation time of the measured object in relation to the results accumulation period. The counter is updated at the same time as the CALLS counter. The presented erlang value in XML report is multiplied by 100.IPATM.M390B2C5 
aal1_success_callsACCUMULATIONINT8The AAL1 SUCCESS CALLS counter shows the number of successful interconnecting termination reservations for ATM AAL1 connections.IPATM.M390B2C2 
aal2_call_amountACCUMULATIONINT8The AAL2 CALL AMOUNT counter shows the number of attempted interconnecting termination reservations for ATM AAL2 connections between MGWs.IPATM.M390B3C1 
aal2_congested_fcallsACCUMULATIONINT8The AAL2 CONGESTED FCALLS counter shows the number of termination reservation attempts for ATM AAL2 connections where the reservation failed due to congestion. The congestion is shown if it occurs in any of the MGWs.IPATM.M390B3C3 
aal2_failed_callsACCUMULATIONINT8The AAL2 FAILED CALLS counter shows the number of failed termination reservations for ATM AAL2 connections. This counter excludes reservations that failed due to congestion.IPATM.M390B3C4 
aal2_seiz_timeACCUMULATIONINT8The AAL2 ERLANGS counter shows the amount of AAL2 traffic between the media gateways in erlangs. That means the total reservation time of the measured object in relation to the results accumulation period. The counter is updated at the same time as the CALLS counter. The presented erlang value in XML report is multiplied by 100.IPATM.M390B3C5 
aal2_success_callsACCUMULATIONINT8The AAL2 SUCCESS CALLS counter shows the number of successful interconnecting termination reservations for ATM AAL2 connections.IPATM.M390B3C2 
corruption_flagACCUMULATIONINT8This flag is set if EXSPRO restarts during the measurement period.IPATM.M390B7C1 
ip_call_amountACCUMULATIONINT8The IPv4 CALL AMOUNT counter shows the number of attempted interconnecting termination reservations for IPv4 connections between MGWs.IPATM.M390B4C1 
ip_congested_fcallsACCUMULATIONINT8The IPv4 CONGESTED FCALLS counter shows the number of termination reservation attempts for IPv4 connections where the reservation failed due to congestion. The congestion is shown if it occurs in any of the MGWs.IPATM.M390B4C3 
ip_failed_callsACCUMULATIONINT8The IPv4 FAILED CALLS counter shows the number of failed termination reservations for IPv4 connections. This counter excludes reservations that failed due to congestion.IPATM.M390B4C4 
ip_seiz_timeACCUMULATIONINT8The IPv4 ERLANGS counter shows the amount of IPv4 traffic between the media gateways in erlangs. That means the total reservation time of the measured object in relation to the results accumulation period. The counter is updated at the same time as the CALLS counter. The presented erlang value in XML report is multiplied by 100.IPATM.M390B4C5 
ip_success_callsACCUMULATIONINT8The IPv4 SUCCESS CALLS counter shows the number of successful interconnecting termination reservations for IPv4 connections.IPATM.M390B4C2 
ipv6_call_amountACCUMULATIONINT8The IPv6 CALL AMOUNT counter shows the number of attempted interconnecting termination reservations for IPv6 connections between MGWs.IPATM.M390B6C1 
ipv6_congested_fcallsACCUMULATIONINT8The IPv6 CONGESTED FCALLS counter shows the number of termination reservation attempts for IPv6 connections where the reservation failed due to congestion. The congestion is shown if itoccurs in any of the MGWs.IPATM.M390B6C3 
ipv6_failed_callsACCUMULATIONINT8The IPv6 FAILED CALLS counter shows the number of failed termination reservations for IPv6 connections. This counter excludes reservations that failed due to congestion.IPATM.M390B6C4 
ipv6_seiz_timeACCUMULATIONINT8The IPv6 ERLANGS counter shows the amount of IPv6 traffic between the media gateways in erlangs. That means the total reservation time of the measured object in relation to the results accumulation period. The counter is updated at the same time as the CALLS counter. The presented erlang value in the XML report is multiplied by 100.IPATM.M390B6C5 
ipv6_success_callsACCUMULATIONINT8The IPv6 SUCCESS CALLS counter shows the number of successful interconnecting termination reservations for IPv6 connections.IPATM.M390B6C2 


MGW.Nokia.GSM.Megaco

The Megaco Interface measurement gives information about the protocol, the interface, and the operational errors, changes on the interface among the MSC Server and Multimedia Gateways.

KPITypeData TypeDescriptionDerivationAdditional Summaries
duplic_transactions_for_requestsACCUMULATIONINT8Represents the total number of duplicated transactions detected in incoming requests during the measurement periodMEG.M354B0C1013nkmgwhmbh
lost_transactions_for_requestsACCUMULATIONINT8Represents the total number of lost transactions in incoming replies during the measurement periodMEG.M354B1C1012nkmgwhmbh
notreliableINTENSITYINTEGERIf counter is sent with value 1 it means that counters for different events and the counters in GENERAL DATA and LINK RELATED POINTERS part are not reliableMEG.M354B2C0nkmgwhmbh
numbofeventsinrepliesACCUMULATIONINT8Total number of the respective event (event presented in localMoid by its code), detected in incoming replies during the measurement period.MEG.M354B1C0nkmgwhmbh
numbofeventsinrequestsACCUMULATIONINT8Total number of the respective event (event presented in localMoid by its code), detected in incoming requests during the measurement period.MEG.M354B0C0nkmgwhmbh
retran_transactions_for_requestsACCUMULATIONINT8Represents the total number of retransmitted transactions in incoming replies during the measurement periodMEG.M354B1C1011nkmgwhmbh
totalnumberoferroneousmessagesACCUMULATIONINT8Represents the total number of erroneous incoming messages (including requests and replies) during the measurement period but does not contain the erroneous events listed under the requests and replies part.MEG.M354B2C1009nkmgwhmbh
totalnumberofhandledmessagesACCUMULATIONINT8Represents the total number of handled messages in incoming requests during the measurement periodMEG.M354B2C1001nkmgwhmbh
totalnumberofsuccmessagesACCUMULATIONINT8Represents the total number of successful incoming messages (including requests and replies) during the measurement period.MEG.M354B2C1002nkmgwhmbh
tothandactionsforrepliesACCUMULATIONINT8Represents the total number of handled actions in incoming replies during the measurement periodMEG.M354B1C1005nkmgwhmbh
tothandactionsforrequestsACCUMULATIONINT8Represents the total number of handled actions in incoming requests during the measurement periodMEG.M354B0C1005nkmgwhmbh
tothandcommandsforrepliesACCUMULATIONINT8Represents the total number of handled commands in incoming replies during the measurement periodMEG.M354B1C1007nkmgwhmbh
tothandcommandsforrequestsACCUMULATIONINT8Represents the total number of handled commands in incoming requests during the measurement periodMEG.M354B0C1007nkmgwhmbh
tothandmessagesforrepliesACCUMULATIONINT8Represents the total number of handled messages in incoming replies during the measurement periodMEG.M354B1C1001nkmgwhmbh
tothandtransactionsforrepliesACCUMULATIONINT8Represents the total number of handled transactions in incoming replies during the measurement periodMEG.M354B1C1003nkmgwhmbh
tothandtransactionsforrequestsACCUMULATIONINT8Represents the total number of handled transactions in incoming requests during the measurement periodMEG.M354B0C1003nkmgwhmbh
totsuccactionsforrepliesACCUMULATIONINT8Represents the total number of successful actions in incoming replies during the measurement periodMEG.M354B1C1006nkmgwhmbh
totsuccactionsforrequestsACCUMULATIONINT8Represents the total number of successful actions in incoming requests during the measurement periodMEG.M354B0C1006nkmgwhmbh
totsucccommandsforrepliesACCUMULATIONINT8Represents the total number of successful commands in incoming replies during the measurement periodMEG.M354B1C1008nkmgwhmbh
totsucccommandsforrequestsACCUMULATIONINT8Represents the total number of successful commands in incoming requests during the measurement periodMEG.M354B0C1008nkmgwhmbh
totsuccmessagesforrepliesACCUMULATIONINT8Represents the total number of successful messages in incoming replies during the measurement periodMEG.M354B1C1002nkmgwhmbh
totsucctransactionsforrepliesACCUMULATIONINT8Represents the total number of successful transactions in incoming replies during the measurement periodMEG.M354B1C1004nkmgwhmbh
totsucctransactionsforrequestsACCUMULATIONINT8Represents the total number of successful transactions in incoming requests during the measurement periodMEG.M354B0C1004nkmgwhmbh


MGW.Nokia.GSM.MSC_circuit_seizure_supervision

Circuit seizure supervision measurement shows the circuits that have been free or reserved during the entire supervision period N.B. There is a secondary key of MSC_circuit

The performance data measurements for this KPI group are recorded against the combination of MGW and MSC_Circuit (msc_circuit_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
cise_state_0_free_ff_reserved2INTENSITYINTEGERState of the circuit (PCM-TSL) during the supervision period.CRTERM.M144B2C3nkmgwhmbh


MGW.Nokia.GSM.MSC_MGW_Events

This section describes the counters of M354: MeO MSC / MGWMNAME / EVENT.N.B. There is a secondary key of MGW_event

The performance data measurements for this KPI group are recorded against the combination of MGW and MGW_Event (EVENT_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
duplictransactionsforrequestsACCUMULATIONINT8Represents the total number of duplicated transactions detected in incoming requests during the measurement periodEVEM.M354B0C1013nkmgwhmbh
losttransactionsforrequestsACCUMULATIONINT8Represents the total number of lost transactions in incoming replies during the measurement periodEVEM.M354B1C1012nkmgwhmbh
notreliableINTENSITYINTEGERIf counter is sent with value 1 it means that counters for different events and the counters in GENERAL DATA and LINK RELATED POINTERS part are not reliable EVEM.M354B2C0nkmgwhmbh
numb_of_events_in_repliesACCUMULATIONINT8Total number of the respective event (event presented in localMoid by its code), detected in incoming replies during the measurement period.EVEM.M354B1C0nkmgwhmbh
numb_of_events_in_requestsACCUMULATIONINT8Total number of the respective event (event presented in localMoid by its code), detected in incoming requests during the measurement period.EVEM.M354B0C0nkmgwhmbh
retrantransactionsforrequestsACCUMULATIONINT8Represents the total number of retransmitted transactions in incoming replies during the measurement periodEVEM.M354B1C1011nkmgwhmbh
totalnumberoferroneousmessagesACCUMULATIONINT8Represents the total number of erroneous incoming messages (including requests and replies) during the measurement period but does not contain the erroneous events listed under the requests and replies part.EVEM.M354B2C1009nkmgwhmbh
totalnumberofhandledmessagesACCUMULATIONINT8Represents the total number of handled messages in incoming requests during the measurement periodEVEM.M354B2C1001nkmgwhmbh
totalnumberofsuccmessagesACCUMULATIONINT8Represents the total number of successful incoming messages (including requests and replies) during the measurement period.EVEM.M354B2C1002nkmgwhmbh
tothandactionsforrepliesACCUMULATIONINT8Represents the total number of handled actions in incoming replies during the measurement periodEVEM.M354B1C1005nkmgwhmbh
tothandactionsforrequestsACCUMULATIONINT8Represents the total number of handled actions in incoming requests during the measurement periodEVEM.M354B0C1005nkmgwhmbh
tothandcommandsforrepliesACCUMULATIONINT8Represents the total number of handled commands in incoming replies during the measurement periodEVEM.M354B1C1007nkmgwhmbh
tothandcommandsforrequestsACCUMULATIONINT8Represents the total number of handled commands in incoming requests during the measurement periodEVEM.M354B0C1007nkmgwhmbh
tothandtransactionsforrepliesACCUMULATIONINT8Represents the total number of handled transactions in incoming replies during the measurement periodEVEM.M354B1C1003nkmgwhmbh
tothandtransactionsforrequestsACCUMULATIONINT8Represents the total number of handled transactions in incoming requests during the measurement periodEVEM.M354B0C1003nkmgwhmbh
totsuccactionsforrepliesACCUMULATIONINT8Represents the total number of successful actions in incoming replies during the measurement periodEVEM.M354B1C1006nkmgwhmbh
totsuccactionsforrequestsACCUMULATIONINT8Represents the total number of successful actions in incoming requests during the measurement periodEVEM.M354B0C1006nkmgwhmbh
totsucccommandsforrepliesACCUMULATIONINT8Represents the total number of successful commands in incoming replies during the measurement periodEVEM.M354B1C1008nkmgwhmbh
totsucccommandsforrequestsACCUMULATIONINT8Represents the total number of successful commands in incoming requests during the measurement periodEVEM.M354B0C1008nkmgwhmbh
totsucctransactionsforrepliesACCUMULATIONINT8Represents the total number of successful transactions in incoming replies during the measurement periodEVEM.M354B1C1004nkmgwhmbh
totsucctransactionsforrequestsACCUMULATIONINT8Represents the total number of successful transactions in incoming requests during the measurement periodEVEM.M354B0C1004nkmgwhmbh


MGW.Nokia.GSM.Simultaneous_Calls

Simultaneous calls on the MGW

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIMUL_MGW_AVG_SIM_CALLACCUMULATIONINT8Shows the average number of simultaneous calls (0...999999999).A sampling is done in each 30 seconds to determine the number of simultaneous calls in the physical MGW address. The average is calculated by dividing the cumulative number of simultaneous calls by the number of samples.SIMCMGW.M396B4C2nkmgwhmbh
SIMUL_MGW_PEAK_SIM_CALLINTENSITYINT8Provides the peak number of simultaneous calls during the measurement period (0...999999999).SIMCMGW.M396B4C3nkmgwhmbh


MGW.Nokia.GSM.Traffic

MGW Traffic related stats

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
MGWTCAT_ANSWERED_TRAFFICERLANGINT8Shows the answered traffic in erlangs. This means that the traffic is counted from the beginning of the conversation phase (ANM/CONNECT ACK) till the end of the call (Release Complete). The field is updated at the end of the call. The value is represented in integers in the XML report and in decimal numbers in the ASCII report.MGWTCP.M395B2C14nkmgwhmbh
MGWTCAT_CALL_ATTEMPTS_ANSWERACCUMULATIONINT8The number of call attempts that were answered, that is, the CONNECT ACK or ANM message was received. This counter is updated at the same time as the CALLS counter.MGWTCP.M395B2C4nkmgwhmbh
MGWTCAT_CALL_ATTEMPTS_RINGINGACCUMULATIONINT8Shows the number of successful call attempts, which reached the ringing phase, that is, ALERTING or ACM/CON message is received. The counter is updated at the same time as the CALLS counter.MGWTCP.M395B2C3nkmgwhmbh
MGWTCAT_CALL_ATTEMPTSACCUMULATIONINT8Shows the number of call attempts. The counter is updated at the end of the call, that is, when the Release Complete message is received. A call attempt is considered only when the MGW is selected for the given category.MGWTCP.M395B2C2nkmgwhmbh
MGWTCAT_CC_GROUP1ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C5nkmgwhmbh
MGWTCAT_CC_GROUP2ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C6nkmgwhmbh
MGWTCAT_CC_GROUP3ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C7nkmgwhmbh
MGWTCAT_CC_GROUP4ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C8nkmgwhmbh
MGWTCAT_CC_GROUP5ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C9nkmgwhmbh
MGWTCAT_CC_GROUP6ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C10nkmgwhmbh
MGWTCAT_CC_GROUP7ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C11nkmgwhmbh
MGWTCAT_CC_GROUP8ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C12nkmgwhmbh
MGWTCAT_DATA_PROV_RESTARTINTENSITYINT8Shows that the Data provider was restarted during the operation.MGWTCP.M395B3C1nkmgwhmbh
MGWTCAT_SUCC_TRAFFICACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCP.M395B2C13nkmgwhmbh
MGWTCAT_TOTAL_TRAFFICERLANGINT8Shows the total traffic in erlangs. The traffic is counted from the beginning of the call till the end of the call (Release Complete) in the circuit reservation (ASSIGNMENT COMPLETE/RAB ASSIGNMENT RESPONSE/IAM). The field is updated at the end of the call. It is given in integers in the XML report and in decimal numbers in the ASCII report.MGWTCP.M395B2C15nkmgwhmbh


MGW.Nokia.GSM.UPD

The UPD measurement gives information about the traffic amount of a specific UPD in a specific MGW. N.B. There is a secondary key of UPD

The performance data measurements for this KPI group are recorded against the combination of MGW and UPD (upd_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
upd_answered_callsACCUMULATIONINT8The number of calls (0...999999) that have reached the conversation state. The field is updated when the first released circuit is released. The field is updated at the same time as the CALLS counter and the RANAP CONNECT message is received from the RNC or BICC ANM/CON / SIP 200ok(invite) message is received from the exchange.UPD.M384B2C5nkmgwhmbh
upd_clear_code_1ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C6nkmgwhmbh
upd_clear_code_2ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C7nkmgwhmbh
upd_clear_code_3ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C8nkmgwhmbh
upd_clear_code_4ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C9nkmgwhmbh
upd_clear_code_5ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C10nkmgwhmbh
upd_clear_code_6ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C11nkmgwhmbh
upd_clear_code_7ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C12nkmgwhmbh
upd_clear_code_8ACCUMULATIONINT8All calls are grouped on the basis of clear code grouping that the user has determined (max. 10 digits). The grouping of clear codes can be changed with the TMH MML command. Note that the user plane destination measurement uses the same clear code grouping as the traffic category measurement. Note that the clear code grouping in field reporting does not apply to clear code grouping in user plane destination measurement. The counter is updated at the same time as the CALLS counter and the call is ended by a clear code which is included in this group. UPD.M384B2C13nkmgwhmbh
upd_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when the data provider in the signalling unit or the signalling unit(s) is restarted during the period and data might not be reliable.UPD.M384B2C15nkmgwhmbh
upd_erlangs_x100ERLANGFLOATThe amount of traffic in the media gateway in erlangs (0.0...999999.9). That means the total reservation time of the measured object in relation to the results accumulation period. The counter is updated at the same time as the CALLS counter. The Erlangs are calculated from the RAB ASSIGNEMENT REQUEST / BICC IAM / SIP invite to RAP RELEASE COMPLETED / BICC REL / SIP Bye or Cancel message. If handover happens than the Erlang is calculated until/from the RANAP RELOCATION REQUIRED message.UPD.M384B2C14nkmgwhmbh
upd_num_of_call_attACCUMULATIONINT8Number of call attempts (0...9999999). The field is updated when the circuit is released. The counter is updated when the UPD is released. UPD.M384B2C4nkmgwhmbh
upd_num_of_call_rejACCUMULATIONINT8Number of the call attempts (0..65535) terminated by MGW and the other MGW will be used after this failure. The MSC Server controls several MGWs. When the first one rejects the resource reservation for some reason and the next MGW is tried, this counter is updated.UPD.M384B2C3nkmgwhmbh


MGW_Neighbour Performance Indicators

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


MGW_Neighbour.Nokia.GSM.Handover

The handover measurement shows the number of different types of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
from_neighbour_mgw_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring MGWSMGW.M345B1C4 
from_neighbour_mgw_okACCUMULATIONINT8Successful handovers from neighbouring MGWSMGW.M345B1C3 
other_legacy_bsc_rnc_from_nokACCUMULATIONINT8Unsuccessful handovers from RNCs/BSCs which are not connected to MGW in same MSC (MGW index is not applicable in this case.)SMGW.M345B2C4 
other_legacy_bsc_rnc_from_okACCUMULATIONINT8Successful handovers from RNCs/BSCs which are not connected to MGW in same MSCSMGW.M345B2C3 
other_legacy_bsc_rnc_to_nokACCUMULATIONINT8Unsuccessful handovers to RNCs/BSCs which are not connected to MGW in same MSC. (MGW index is not applicable in this case.)SMGW.M345B2C2 
other_legacy_bsc_rnc_to_okACCUMULATIONINT8Successful handovers to RNCs/BSCs which are not connected to MGW in same MSCSMGW.M345B2C1 
other_mgw_inter_mss_from_nokACCUMULATIONINT8Unsuccessful handovers from MGWs connected to other MSC (in incoming inter MSC handover case we do not know the old MGW index in MSC-B.)SMGW.M345B2C9 
other_mgw_inter_mss_from_okACCUMULATIONINT8Successful handovers from MGWs in other MSCSMGW.M345B2C8 
other_mgw_inter_mss_to_nokACCUMULATIONINT8Unsuccessful handovers to MGWs connected to other MSC. (in outgoing inter MSC handover case we do not know the new MGW index in MSC-A)SMGW.M345B2C7 
other_mgw_inter_mss_to_okACCUMULATIONINT8Successful handovers to MGWs in other MSCSMGW.M345B2C6 
other_mgw_intra_mss_to_nokACCUMULATIONINT8Unsuccessful intra MSC handovers to MGWs when the MGW index is not known because the handover failed before or during the resource reservation.SMGW.M345B2C5 
toneighbourmgwnokACCUMULATIONINT8Unsuccessful handovers to neighbouring MGWSMGW.M345B1C2 
toneighbourmgwokACCUMULATIONINT8Successful handovers to neighbouring MGWSMGW.M345B1C1 


MSC Performance Indicators

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


MSC.Nokia.GSM.Cell

This section describes the counters of M22: MeO MSC.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ave_inc_conINTENSITYFLOATThe average incoming call conversation time in seconds.CELLMSC.M22B2C3nkmtbh
ave_int_conINTENSITYFLOATThe average internal call conversation time in seconds.CELLMSC.M22B2C1nkmtbh
ave_out_conINTENSITYFLOATThe average outgoing call conversation time in seconds.CELLMSC.M22B2C2nkmtbh
ave_pagetimeINTENSITYFLOATThe average paging time of a subscriber for successful calls.CELLMSC.M22B3C1nkmtbh
ave_trans_conINTENSITYFLOATAverage transit conversation time.CELLMSC.M22B2C4nkmtbh
cellmeas_corrupt_messageINTENSITYINTEGERThis tag appears with value 1 when there are no records or the whole report is corrupted.CELLMSC.M22B3C2nkmtbh


MSC.Nokia.GSM.Circuit_Seizure_Supervision

Circuit seizure supervision measurement shows the circuits that have been free or reserved during the entire supervision period (1 to 7 days). This group has a secondary key of msc_circuit.

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
statusINTENSITYINTEGER(Obsolete in M13.5, CRTSL block now supported under TSL object) Circuit status. 0 = circuit is not seized, -1 = circuit is seizedobsolete.obsoletenkmtbh


MSC.Nokia.GSM.Clear_Code_Destination

This measurement contains the measurement results from the clear codes of the destinations measurement, which is part of field reporting. N.B. There is a secondary key of msc_clear_code and also number_destination

The performance data measurements for this KPI group are recorded against the combination of MSC, MSC_Clear_Code (msc_clear_code_id) and Number_Destination (number_destination_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_in_ringACCUMULATIONINT8The number of calls ending with clear code in ring phaseCCDES.M132B2C2nkmtbh
calls_in_signalACCUMULATIONINT8The number of calls ending with clear code in signalling phaseCCDES.M132B2C1nkmtbh
calls_in_speechACCUMULATIONINT8The number of calls ending with clear code in speech phaseCCDES.M132B2C3nkmtbh


MSC.Nokia.GSM.Clear_Code_Group_Destination

This group contains information about the number of calls which have ended with each clear code group per destination. N.B. There is a secondary key of number_destination

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_clr_grp_1ACCUMULATIONINT8The number of calls ended in clear code group 1.DESTCG.M133B2C2nkmtbh
calls_clr_grp_2ACCUMULATIONINT8The number of calls ended in clear code group 2.DESTCG.M133B2C3nkmtbh
calls_clr_grp_3ACCUMULATIONINT8The number of calls ended in clear code group 3.DESTCG.M133B2C4nkmtbh
calls_clr_grp_4ACCUMULATIONINT8The number of calls ended in clear code group 4.DESTCG.M133B2C5nkmtbh
calls_clr_grp_5ACCUMULATIONINT8The number of calls ended in clear code group 5.DESTCG.M133B2C6nkmtbh
calls_clr_grp_6ACCUMULATIONINT8The number of calls ended in clear code group 6.DESTCG.M133B2C7nkmtbh
calls_clr_grp_7ACCUMULATIONINT8The number of calls ended in clear code group 7.DESTCG.M133B2C8nkmtbh
calls_clr_grp_8ACCUMULATIONINT8The number of calls ended in clear code group 8.DESTCG.M133B2C9nkmtbh


MSC.Nokia.GSM.Clear_Code

This measurement contains the measurement results from the clear codes of the calls measurement, which is part of field reporting. It contains information about the number of calls ended with each clear code.N.B. There is a secondary key of msc_clear_code

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_in_ringACCUMULATIONINT8The number of calls ending with clear code in ring phaseCCMEA.M131B2C2nkmtbh
calls_in_signalACCUMULATIONINT8The number of calls ending with clear code in signalling phaseCCMEA.M131B2C1nkmtbh
calls_in_speechACCUMULATIONINT8The number of calls ending with clear code in speech phaseCCMEA.M131B2C3nkmtbh


MSC.Nokia.GSM.Codec_usage

Codec usage data. N.B this data has a secondary key of codec.

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
mgwc_bidsACCUMULATIONINT8This counter shows how many times the codec is used in the MSS per termination at MSS level. The counter is updated when the MSS assigns a codec to a termination in the MGW.MGWCU.M389B2C2nkmtbh
mgwc_data_prov_restartedACCUMULATIONINT8If the statistics data provider program block is restarted in any of the signalling unit(s) during the period, the M389B2C3 counter is written (with value '1') under every record. Otherwise, the counter is omitted.MGWCU.M389B2C3nkmtbh


MSC.Nokia.GSM.Control_Unit_Load

This table contains the measurement results from the control unit measurements. N.B. There is a secondary key of control_unit

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
cntll_invalid_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the actual record is invalid.CNTLLM.M118B2C7nkmtbh
failed_calls_extACCUMULATIONINT8The number of calls ended in the external error condition.CNTLLM.M118B2C5nkmtbh
failed_calls_intACCUMULATIONINT8The number of calls ended in the internal error condition.CNTLLM.M118B2C4nkmtbh
failed_callsINTENSITYFLOATThe failed calls percentageCNTLLM.M118B2C2 / 10nkmtbh
total_callsACCUMULATIONINT8The total number of calls.CNTLLM.M118B2C3nkmtbh
traffic_intensityERLANGFLOATThe traffic intensityCNTLLM.M118B2C6 / 10nkmtbh


MSC.Nokia.GSM.Control_Unit

This table contains the measurement results from the control unit measurements. N.B. There is a secondary key of control_unit

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_successful_callsPERCENTAGEFLOATPercentage successful callspercentok({cntl_accep}, {cntl_calls})nkmtbh
%_unsuccessful_callsPERCENTAGEFLOATPercentage unsuccessful callspercentfail(({cntl_sfail} + {cntl_efail}), {cntl_calls})nkmtbh
avr_traf_erlangERLANGFLOATThe average traffic in erlangsCNTL.M18B2C9 / 100.0nkmtbh
cntl_accepACCUMULATIONINT8Number of successful call attempts (0...999999999), clear codes 0...3FF. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the call is ended by clear code 0...3FF.CNTL.M18B2C3nkmtbh
cntl_answACCUMULATIONINT8The number of call attempts that have reached the conversation state.CNTL.M18B2C5nkmtbh
cntl_callsACCUMULATIONINT8Number of call attempts (0...999999999). The field is updated when the circuit is released. The counter is updated: during the following events: receiving the BSSAP RELEASE COMPLETE message from the BSC. receiving the RANAP Iu RELEASE COMPLETE message froCNTL.M18B2C2nkmtbh
cntl_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when the data provider in the signalling unit or signalling unit(s) is restarted during the period and data might not be reliable.CNTL.M18B2C11nkmtbh
cntl_efailACCUMULATIONINT8Number of call attempts (0...999999999) that have terminated in a trunk circuit error, clear codes 800...BFF.CNTL.M18B2C8nkmtbh
cntl_invalid_recordINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid.CNTL.M18B2C10nkmtbh
cntl_sfailACCUMULATIONINT8Number of call attempts (0...999999999) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the circuit is released. The counter is updated at the same time when the CALLS counter and the call is ended by clear codCNTL.M18B2C6nkmtbh
int_err_callsACCUMULATIONINT8Calls ended in the internal error condition.CNTL.M18B2C7nkmtbh
RE_PKTS_64ACCUMULATIONFLOATDescription Shows the number of the average H.248 context utilization during the measurement period (0...99999999). The average is taken by counting the active context periodically and then taking the arithmetic mean. It is available only for CCSU and SIGU unit.CNTL.M18B2C12nkmtbh
RE_PKTS_65_127INTENSITYFLOATDescription Shows the number of the peak context utilization during the measurement period (0...99999999). Only available for CCSU and SIGU unit.CNTL.M18B2C13nkmtbh
unsuccessful_callsACCUMULATIONINT8Number of call attempts that were unsuccessful. Subscriber errors + trunk code errors{cntl_sfail} + {cntl_efail}nkmtbh


MSC.Nokia.GSM.CSSMT

Call setup service mean time data

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_successful_bidsPERCENTAGEFLOATPercentage call setup service attempts that were successfulpercentok({cssmt_succ_bids}, ({cssmt_succ_bids} + {cssmt_failed_bids}))nkmtbh
%_unsuccessful_bidsPERCENTAGEFLOATPercentage call setup service attempts that were unsuccessfulpercentfail({cssmt_failed_bids}, ({cssmt_succ_bids} + {cssmt_failed_bids}))nkmtbh
attempts_call_setup_serviceACCUMULATIONINT8Number of call setup service attempts.{cssmt_succ_bids} + {cssmt_failed_bids}nkmtbh
cssmt_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when the data provider in the signalling unit or the signalling unit(s) is restarted during the report period, and data might not be reliable.CSSM.M387B2C5nkmtbh
cssmt_failed_bidsACCUMULATIONINT8Number of unsuccessful call setup service attempts in the MSC level.CSSM.M387B2C3nkmtbh
cssmt_failed_mean_timeACCUMULATIONINT8Mean time of unsuccessful call setup service attempts in seconds in ASCII reports and in 10 ms in XML reports. Mean time is calculated by dividing the value of the unsuccessful total call setup service time reservation by the value of unsuccessful call seCSSM.M387B2C4nkmtbh
cssmt_succ_bidsACCUMULATIONINT8Number of successful call setup service attempts in MSC level.CSSM.M387B2C1nkmtbh
cssmt_succ_mean_timeACCUMULATIONINT8Mean time of successful call setup service attempts in seconds in ASCII reports and in 10 ms in XML reports. Mean time is calculated by dividing the value of the successful total call setup service time reservation by the value of successful call setup seCSSM.M387B2C2nkmtbh


MSC.Nokia.GSM.CSTS

Call setup time and success data

KPITypeData TypeDescriptionDerivationAdditional Summaries
csts_all_succ_setupsACCUMULATIONINT8Number of all successful setup attempts during the report period. The counter is updated when the signalling phase is ended, that is, before sending the ALERT message.CSTS.M386B2C3nkmtbh
csts_data_prov_restartedACCUMULATIONINT8If the result corruption flag is true, this means that the data provider in signalling unit or signalling unit(s) is restarted during the period. In this case, M386B2C30 counter is written (with value '1'). Otherwise, the counter is omitted.CSTS.M386B2C30nkmtbh
csts_ext_fail_unsucc_setup_aveINTENSITYFLOATThe average call setup time of the durations of the external released connections during the period. Clear code range for internal failure released connection: 800...BFF. The unit of measure is seconds in ASCII reports and 10 milliseconds in XML reports.CSTS.M386B2C22nkmtbh
csts_extfail_all_unsucc_setupACCUMULATIONINT8Number of failed call setup attempts due to external failure. The counter is updated when the call is interrupted during the setup phase, and the clear code is in the range of 800-BFF. It means that the MSC either receives the CM_SERVICE_ABORT message, reCSTS.M386B2C18nkmtbh
csts_extfail_long_unsucc_setupACCUMULATIONINT8Number of failed call setup attempts due to external failure, and the call setup time is over the time defined by the LONG_SETUP_TIMEPRFILE parameter. The counter is updated when the call is interrupted during the setup phase, and the clear code is in theCSTS.M386B2C20nkmtbh
csts_extfail_x_unsucc_setuptimACCUMULATIONINT8The longest call setup time in report period for external failure released connections. Clear code range for internal failure released connection: 800...BFF. The unit of time in ASCII report is seconds, and in XML reports, it is 10 milliseconds.CSTS.M386B2C21nkmtbh
csts_int_fail_unsucc_setup_aveINTENSITYFLOATThe average time of the durations of the internal released connections during the period. Clear code range for internal failure released connection: 400...7FF. The unit of time in ASCII report is seconds, and in XML reports, it is 10 milliseconds.CSTS.M386B2C17nkmtbh
csts_intfail_all_unsucc_setupACCUMULATIONINT8Number of failed call setup attempts due to internal failure. The counter is updated when the call is interrupted during the setup phase, and the clear code is in the range of 400-7FF. It means that the MSC either receives the CM_SERVICE_ABORT message, reCSTS.M386B2C13nkmtbh
csts_intfail_long_unsucc_setupACCUMULATIONINT8Number of failed call setup attempts due to internal failure, and the call setup time is over the time defined by the LONG_SETUP_TIMEPRFILE parameter. The counter is updated when the call is interrupted during the setup phase, and the clear code is in theCSTS.M386B2C15nkmtbh
csts_intfail_x_unsucc_setuptimACCUMULATIONINT8The longest call setup time in the report period for internal failure released connections. Clear code range for internal failure released connection: 400...7FF. The unit of time in ASCII report is seconds, and in XML reports, it is 10 milliseconds.CSTS.M386B2C16nkmtbh
csts_long_setup_timeACCUMULATIONINT8Long setup time is a PRFILE parameter which describes the time limit for the long call setups, that is, if the call setup time exceeds long setup time limit, it will be counted in M386B2C4 counter. The unit oftime in ASCII report is seconds, in XML reportCSTS.M386B2C2nkmtbh
csts_long_succ_setupsACCUMULATIONINT8Number of long successful setups when the setup time is over the time defined by the PRFILE parameter. The counter is updated when the signalling phase ends, that is before sending the ALERT message.CSTS.M386B2C4nkmtbh
csts_max_succ_setup_timeACCUMULATIONINT8The longest successful setup time in the report period. The unit of time in ASCII report is seconds, in XML reports, it is 10 milliseconds.CSTS.M386B2C6nkmtbh
csts_min_succ_setup_timeACCUMULATIONINT8The shortest successful setup time in report period. The unit of time in ASCII report is seconds, in XML reports, it is 10 milliseconds.CSTS.M386B2C5nkmtbh
csts_norm_rl_all_unsucc_setupsACCUMULATIONINT8Number of failed call setup attempts that have terminated in a normal release.CSTS.M386B2C8nkmtbh
csts_norm_rl_long_unsucc_setupACCUMULATIONINT8Number of failed call setup attempts that have terminated in normal release, and the setup time is over the defined time by the LONG_SETUP_TIME PRFILE parameter.CSTS.M386B2C10nkmtbh
csts_norm_rl_unsucc_setup_aveINTENSITYFLOATThe average call setup time of the failed call setup attempts, which terminated in the normal release (where the clear code is in the range of 001-3FF). The unit of the average call setup time in ASCII report is seconds, in XML reports, it is 10 millisecondCSTS.M386B2C12nkmtbh
csts_norm_rl_x_unsucc_setuptimACCUMULATIONINT8The longest call setup time from the failed call setup attempts, which terminated in the normal release (where the clear code is in the range of 001-3FF). The unit of time in ASCII report is seconds, in XML reports, it is 10 milliseconds.CSTS.M386B2C11nkmtbh
csts_subsfail_all_unsucc_setupACCUMULATIONINT8Number of failed call setup attempts due to subscriber failure.CSTS.M386B2C23nkmtbh
csts_subsfail_long_unsuc_setupACCUMULATIONINT8Number of failed call setup attempts due to subscriber failure, and the call setup time is over the defined time by the LONG_SETUP_TIMEPRFILE parameter.CSTS.M386B2C25nkmtbh
csts_subsfail_unsucc_setup_aveINTENSITYFLOATThe average call setup time of the durations of the subscriber released connections during the period. Clear code range for internal failure released connection: C00...FFF. The unit of time in ASCII report is seconds, in XML reports it is 10 milliseconds.CSTS.M386B2C27nkmtbh
csts_subsfail_x_unsuc_setuptimACCUMULATIONINT8The longest call setup time in the report period for subscriber failure released connections. Clear code range for internal failure released connection: C00...FFF. The unit of time in ASCII report is seconds, in XML reports it is 10 milliseconds.CSTS.M386B2C26nkmtbh
csts_succ_setup_aveACCUMULATIONINT8The longest successful setup time in the report period. The unit of time in ASCII report is seconds, in XML reports, it is 10 milliseconds.CSTS.M386B2C7nkmtbh


MSC.Nokia.GSM.Data_Clear_Code_Destination

The measurement shows how the data call clear codes of a given number destination are divided into clear code groups. N.B. There is a secondary key of number_destination

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
cc_group_1ACCUMULATIONINT8The number of calls ended in clear code group 1.DCALL.M304B2C2nkmtbh
cc_group_2ACCUMULATIONINT8The number of calls ended in clear code group 2.DCALL.M304B2C3nkmtbh
cc_group_3ACCUMULATIONINT8The number of calls ended in clear code group 3.DCALL.M304B2C4nkmtbh
cc_group_4ACCUMULATIONINT8The number of calls ended in clear code group 4.DCALL.M304B2C5nkmtbh
cc_group_5ACCUMULATIONINT8The number of calls ended in clear code group 5.DCALL.M304B2C6nkmtbh
cc_group_6ACCUMULATIONINT8The number of calls ended in clear code group 6.DCALL.M304B2C7nkmtbh
cc_group_7ACCUMULATIONINT8The number of calls ended in clear code group 7.DCALL.M304B2C8nkmtbh
cc_group_8ACCUMULATIONINT8The number of calls ended in clear code group 8.DCALL.M304B2C9nkmtbh


MSC.Nokia.GSM.Data_Clear_Code

The measurement shows all occurrences of the internal data call clear codes used. Clear code distribution is presented according to the call phase. N.B. There is a secondary key of msc_clear_code

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
cc_ring_phaseACCUMULATIONINT8The number of calls ending with clear code in ring phaseDATA.M305B2C2nkmtbh
cc_signal_phaseACCUMULATIONINT8The number of calls ending with clear code in signalling phaseDATA.M305B2C1nkmtbh
cc_speech_phaseACCUMULATIONINT8The number of calls ending with clear code in speech phaseDATA.M305B2C3nkmtbh


MSC.Nokia.GSM.Data_Service

The Data service unit measurement measures the data traffic intensity for different call types and data service units.N.B. There is a secondary key of call_type

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
dsu_invalid_recordINTENSITYINTEGERThe tag appears only with value 1 when every counter in the group contains the 0xFFFFFFFF value.DSE.M306B2C10nkmtbh
nbr_call_att_ansACCUMULATIONINT8Number of call attempts that have been answered.DSE.M306B2C4nkmtbh
nbr_call_att_startedACCUMULATIONINT8Number of call attempts that have been started during the measurement period.DSE.M306B2C2nkmtbh
nbr_fail_home_exchgACCUMULATIONINT8Number of failed call attempts terminated in an error in the home exchange, clear codes 400...7FF.DSE.M306B2C6nkmtbh
nbr_fail_subsc_errACCUMULATIONINT8Number of failed call attempts that have terminated in a subscriber, clear codes C00...FFF.DSE.M306B2C5nkmtbh
nbr_fail_trunc_circuitACCUMULATIONINT8Number of failed call attempts that have terminated in an error on the trunk circuit, clear codes 800...BFF.DSE.M306B2C7nkmtbh
nbr_success_call_attACCUMULATIONINT8Number of successful call attempts, clear codes 0...3FF.DSE.M306B2C3nkmtbh
nbr_success_syncACCUMULATIONINT8Number of successful synchronisations between data terminals.DSE.M306B2C8nkmtbh
traffic_intensityERLANGFLOATTraffic intensityDSE.M306B2C9 / 100.0nkmtbh


MSC.Nokia.GSM.Destination_to_Destination

This measurement contains the measurement results of the destination to destination measurements.N.B. There is a secondary key of incoming_number_destination and also outgoing number destination

The performance data measurements for this KPI group are recorded against the combination of MSC, Incoming_Number_Destination (INDESTTYPE_ID) and Outgoing_Number_Destination (OUTDESTTYPE_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ans_callsACCUMULATIONINT8Answered calls.DTD.M25B2C8nkmtbh
avr_traf_erlangERLANGFLOATThe average traffic in erlangsDTD.M25B2C12 / 100.0nkmtbh
dtd_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when the data provider in the signalling unit or the signalling unit(s) is restarted during the period and data might not be reliable.DTD.M25B2C15nkmtbh
dtd_invalid_recordINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid or if the destination information is corrupted.DTD.M25B2C13nkmtbh
dtd_overl_cntrl_activeINTENSITYINTEGERThis tag appears at the end of the given counter group if the field value is 10 (In this case the Automatic Overload Control of Statistics has been activated.).DTD.M25B2C14nkmtbh
ext_err_callsACCUMULATIONINT8Calls ended in the external error condition.DTD.M25B2C11nkmtbh
int_err_callsACCUMULATIONINT8Calls ended in the internal error condition.DTD.M25B2C10nkmtbh
nbr_callsACCUMULATIONINT8The number of calls made.DTD.M25B2C5nkmtbh
subsc_errACCUMULATIONINT8The number of subscriber errors.DTD.M25B2C9nkmtbh
succ_callsACCUMULATIONINT8The number of successful calls.DTD.M25B2C6nkmtbh


MSC.Nokia.GSM.FQDN_Clearcodes

FQDN clearcode data. This kpi group has a secondary key of msc clear code.

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
sscc_ringACCUMULATIONINT8(Obsolete in M13.5, KPI Group now parked under FQDN object) The number of clear codes in the ringing phaseobsolete.obsoletenkmtbh
sscc_signallingACCUMULATIONINT8(Obsolete in M13.5, KPI Group now parked under FQDN object) The number of clear codes in the signalling phaseobsolete.obsoletenkmtbh
sscc_speechACCUMULATIONINT8(Obsolete in M13.5, KPI Group now parked under FQDN object) The number of clear codes in the speech phaseobsolete.obsoletenkmtbh


MSC.Nokia.GSM.Gapped_In_Services_Destination

This section describes the key columns and counters of M134: MeO MSC / DEST. N.B. There is a secondary key of number_destination

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
ingap_manualACCUMULATIONINT8The number of calls gapped by the operator.IND.M134B2C4nkmtbh
ingap_scp_overloadACCUMULATIONINT8The number of gapped calls due to SCP overload.IND.M134B2C3nkmtbh


MSC.Nokia.GSM.Gapped_In_Services_Service

This section describes the key columns and counters of M134. N.B. There is a secondary key of IN_service

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
ingap_manualACCUMULATIONINT8The number of calls gapped by the operator.INS.M134B2C4nkmtbh
ingap_scp_overloadACCUMULATIONINT8The number of gapped calls due to SCP overload.INS.M134B2C3nkmtbh


MSC.Nokia.GSM.Gapped_in_Services

This measurement contains information about the restrictions of the Intelligent Network services.

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_operatorACCUMULATIONINT8Obsolete in M13.5 - The number of calls gapped by the operator.INGAP.obsoletenkmtbh
calls_spcACCUMULATIONINT8The number of gapped calls due to SCP overload.INGAP.M134B2C3nkmtbh


MSC.Nokia.GSM.GBS_Data_AIUR

This section describes the key columns and counters of M307: MeO MSC / AIUR.N.B. There is a secondary key of AIUR

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
channel_coding_144ACCUMULATIONINT8At least 14.4 KBIT/S channel coding is accepted.GBSAIUR.M307B3C12nkmtbh
channel_coding_96ACCUMULATIONINT8Only 9.6 KBIT/S channel coding is accepted.GBSAIUR.M307B3C11nkmtbh
dwngrd_call_att_144ACCUMULATIONINT8Number of successful downgraded call attempts using 14.4 KBIT/S channel coding.GBSAIUR.M307B3C8nkmtbh
dwngrd_call_att_96ACCUMULATIONINT8Number of successful downgraded call attempts using 9.6 KBIT/S channel coding.GBSAIUR.M307B3C6nkmtbh
dwngrd_config_changes_144ACCUMULATIONINT8Number of channel configuration changes to 14.4 KBIT/S during the measurement period.GBSAIUR.M307B3C17nkmtbh
dwngrd_config_changes_96ACCUMULATIONINT8Number of channel configuration changes to 9.6 KBIT/S during the measurement period.GBSAIUR.M307B3C15nkmtbh
max_nbr_tch_1ACCUMULATIONINT8Number of times the maximum number of 1 TCH was allowed by MS.GBSAIUR.M307B3C20nkmtbh
max_nbr_tch_2ACCUMULATIONINT8Number of times the maximum number of 2 TCH was allowed by MS.GBSAIUR.M307B3C21nkmtbh
max_nbr_tch_3ACCUMULATIONINT8Number of times the maximum number of 3 TCH was allowed by MS.GBSAIUR.M307B3C22nkmtbh
max_nbr_tch_4ACCUMULATIONINT8Number of times the maximum number of 4 TCH was allowed by MS.GBSAIUR.M307B3C23nkmtbh
max_nbr_tch_5ACCUMULATIONINT8Number of times the maximum number of 5 TCH was allowed by MS.GBSAIUR.M307B3C24nkmtbh
max_nbr_tch_6ACCUMULATIONINT8Number of times the maximum number of 6 TCH was allowed by MS.GBSAIUR.M307B3C25nkmtbh
max_nbr_tch_7ACCUMULATIONINT8Number of times the maximum number of 7 TCH was allowed by MS.GBSAIUR.M307B3C26nkmtbh
max_nbr_tch_8ACCUMULATIONINT8Number of times the maximum number of 8 TCH was allowed by MS.GBSAIUR.M307B3C27nkmtbh
nbr_setup_att_144ACCUMULATIONINT8Number of setup attempts, where highest acceptable channel coding is 14.4 KBIT/S (from MS).GBSAIUR.M307B3C3nkmtbh
nbr_setup_att_96ACCUMULATIONINT8Number of setup attempts, where highest acceptable channel coding is 9.6 KBIT/S (from MS).GBSAIUR.M307B3C2nkmtbh
req_config_changes_144ACCUMULATIONINT8Number of channel configuration changes to 14.4 KBIT/S during the measurement period.GBSAIUR.M307B3C16nkmtbh
req_config_changes_96ACCUMULATIONINT8Number of channel configuration changes to 9.6 KBIT/S during the measurement period.GBSAIUR.M307B3C14nkmtbh
succ_call_att_144ACCUMULATIONINT8Number of successful call attempts using 14.4 KBIT/S channel coding.GBSAIUR.M307B3C7nkmtbh
succ_call_att_96ACCUMULATIONINT8Number of successful call attempts using 9.6 KBIT/S channel coding.GBSAIUR.M307B3C5nkmtbh


MSC.Nokia.GSM.GBS_Data_FNUR

This section describes the key columns and counters of M307: MeO MSC / FNUR.N.B. There is a secondary key of FNUR

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
max_nbr_tch_1ACCUMULATIONINT8Number of times the maximum number of 1 TCH was allowed by MS.GBSFNUR.M307B2C11nkmtbh
max_nbr_tch_2ACCUMULATIONINT8Number of times the maximum number of 2 TCH was allowed by MS.GBSFNUR.M307B2C12nkmtbh
max_nbr_tch_3ACCUMULATIONINT8Number of times the maximum number of 3 TCH was allowed by MS.GBSFNUR.M307B2C13nkmtbh
max_nbr_tch_4ACCUMULATIONINT8Number of times the maximum number of 4 TCH was allowed by MS.GBSFNUR.M307B2C14nkmtbh
max_nbr_tch_5ACCUMULATIONINT8Number of times the maximum number of 5 TCH was allowed by MS.GBSFNUR.M307B2C15nkmtbh
max_nbr_tch_6ACCUMULATIONINT8Number of times the maximum number of 6 TCH was allowed by MS.GBSFNUR.M307B2C16nkmtbh
max_nbr_tch_7ACCUMULATIONINT8Number of times the maximum number of 7 TCH was allowed by MS.GBSFNUR.M307B2C17nkmtbh
max_nbr_tch_8ACCUMULATIONINT8Number of times the maximum number of 8 TCH was allowed by MS.GBSFNUR.M307B2C18nkmtbh
nbr_channel_144ACCUMULATIONINT8Number of channel coding configuration changes resulting the use of 14.4 KBIT/S channel coding.GBSFNUR.M307B2C9nkmtbh
nbr_channel_96ACCUMULATIONINT8Number of channel coding configuration changes resulting the use of 9.6 KBIT/S channel coding.GBSFNUR.M307B2C8nkmtbh
nbr_setup_att_144ACCUMULATIONINT8Number of setup attempts (0..999999) that have been started during the measurement period are counted per requested data rate. The requested data rate is updated according to highest accepted channel.GBSFNUR.M307B2C3nkmtbh
nbr_setup_att_96ACCUMULATIONINT8Number of setup attempts (0..999999) that have been started during the measurement period are counted per requested data rate. The requested data rate is updated according to highest accepted channel.GBSFNUR.M307B2C2nkmtbh
used_channel_144ACCUMULATIONINT8Used channel coding 14.4 KBIT/S.GBSFNUR.M307B2C6nkmtbh
used_channel_96ACCUMULATIONINT8Used channel coding is 9.6 KBIT/S.GBSFNUR.M307B2C5nkmtbh


MSC.Nokia.GSM.GBS_Data_UMTS_AIUR

This section describes the key columns and counters of M307: MeO MSC / UMTSAIUR. N.B. There is a secondary key of AIUR.

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
dwngrd_rate_changeACCUMULATIONINT8The number of downgrade rate change to this speedUMTSAI.M307B5C6nkmtbh
dwngrd_succ_call_attACCUMULATIONINT8The number of successful call attempts - usage downgradeUMTSAI.M307B5C4nkmtbh
req_rate_changeACCUMULATIONINT8The number of request rate change to this speed which is equal to the requested speedUMTSAI.M307B5C5nkmtbh
req_succ_call_attemptACCUMULATIONINT8The number of successful call attempts - usage requiredUMTSAI.M307B5C3nkmtbh
succ_call_attemptACCUMULATIONINT8Number of setup attemptsUMTSAI.M307B5C2nkmtbh


MSC.Nokia.GSM.GBS_Data_UMTS_FNUR

This section describes the key columns and counters of M307: MeO MSC / UMTSFNUR.N.B. There is a secondary key of FNUR

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
nbr_fallbackACCUMULATIONINT8The number of fallbacks from 33.6 in transparentconnectionUMTSFN.M307B4C5nkmtbh
nbr_hoACCUMULATIONINT8The number of handoversUMTSFN.M307B4C4nkmtbh
nbr_setup_attemptACCUMULATIONINT8Number of setup attemptsUMTSFN.M307B4C2nkmtbh
nbr_succ_call_attemptACCUMULATIONINT8The number of successful setup attemptsUMTSFN.M307B4C3nkmtbh


MSC.Nokia.GSM.GSM_UMTS_Handovers

This measurement contains the information about the number of the MSC and BSC controlled successful and unsuccessful handovers. Specifically GSM - UMTS

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_succ_i_msc_gsm_umts_hoPERCENTAGEFLOATPercentage successful intra-MSC GSM-UMTS Handoverspercentok({succ_i_msc_gsm_umts_ho}, ({succ_i_msc_gsm_umts_ho} + {unsucc_i_msc_gsm_umts_ho}))nkmtbh
%_succ_inc_e_msc_gsm_umts_hoPERCENTAGEFLOATPercentage successful inter-MSC GSM-UMTS Handoverspercentok({succ_inc_e_msc_gsm_umts_ho}, ({succ_inc_e_msc_gsm_umts_ho} + {unsucc_inc_e_msc_gsm_umts_ho}))nkmtbh
%_succ_inc_e_plmn_gsm_umts_hoPERCENTAGEFLOATPercentage successful outgoing inter-PLMN GSM-UMTS handovers.percentok({succ_inc_e_plmn_gsm_umts_ho}, ({succ_inc_e_plmn_gsm_umts_ho} + {unsucc_inc_e_plmn_gsm_umts_ho}))nkmtbh
%_succ_out_e_msc_gsm_umts_hoPERCENTAGEFLOATPercentage successful outgoing inter-MSC GSM-UMTS handovers.percentok({succ_out_e_msc_gsm_umts_ho}, ({succ_out_e_msc_gsm_umts_ho} + {unsucc_out_e_msc_gsm_umts_ho}))nkmtbh
%_succ_out_e_plmn_gsm_umts_hoPERCENTAGEFLOATPercentage successful outgoing inter-PLMN GSM-UMTS handoverspercentok({succ_out_e_plmn_gsm_umts_ho}, ({succ_out_e_plmn_gsm_umts_ho} + {unsucc_out_e_plmn_gsm_umts_ho}))nkmtbh
%_succ_plmn_msc_gsm_umts_hoPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC GSM-UMTS handovers.percentok({succ_plmn_msc_gsm_umts_ho}, ({succ_plmn_msc_gsm_umts_ho} + {unsucc_plmn_msc_gsm_umts_ho}))nkmtbh
%_unsucc_i_msc_gsm_umts_hoPERCENTAGEFLOATPercentage unsuccessful intra-MSC GSM-UMTS Handoverspercentfail({unsucc_i_msc_gsm_umts_ho}, ({succ_i_msc_gsm_umts_ho} + {unsucc_i_msc_gsm_umts_ho}))nkmtbh
%_unsucc_inc_e_msc_gsm_umts_hoPERCENTAGEFLOATPercentage unsuccessful inter-MSC GSM-UMTS Handoverspercentfail({unsucc_inc_e_msc_gsm_umts_ho}, ({succ_inc_e_msc_gsm_umts_ho} + {unsucc_inc_e_msc_gsm_umts_ho}))nkmtbh
%_unsucc_inc_e_plmn_gsm_umts_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN GSM-UMTS handovers.percentfail({unsucc_inc_e_plmn_gsm_umts_ho}, ({succ_inc_e_plmn_gsm_umts_ho} + {unsucc_inc_e_plmn_gsm_umts_ho}))nkmtbh
%_unsucc_out_e_msc_gsm_umts_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC GSM-UMTS handovers.percentfail({unsucc_out_e_msc_gsm_umts_ho}, ({succ_out_e_msc_gsm_umts_ho} + {unsucc_out_e_msc_gsm_umts_ho}))nkmtbh
%_unsucc_out_e_plmn_gsm_umts_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN GSM-UMTS handoverspercentfail({unsucc_out_e_plmn_gsm_umts_ho}, ({succ_out_e_plmn_gsm_umts_ho} + {unsucc_out_e_plmn_gsm_umts_ho}))nkmtbh
%_unsucc_plmn_msc_gsm_umts_hoPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC GSM-UMTS handovers.percentfail({unsucc_plmn_msc_gsm_umts_ho}, ({succ_plmn_msc_gsm_umts_ho} + {unsucc_plmn_msc_gsm_umts_ho}))nkmtbh
dropped_callsACCUMULATIONINT8Number of calls dropped.{iamscgsmtoumtsclear} + {ieplmniamscgsmtoumtsclear} + {iniemscgsmtoumtsclear} + {outiemscgsmtoumtsclear} + {inieplmngsmtoumtsclear} + {outieplmngsmtoumtsclear}nkmtbh
iamscgsmtoumtsclearACCUMULATIONINT8Number of calls dropped due to failed intra-MSC GSM-UMTS handoversHO1.M81B3C66nkmtbh
iamscgsmtoumtsreestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC GSM-UMTS handoversHO1.M81B3C65nkmtbh
ieplmniamscgsmtoumtsclearACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC GSM-UMTS handoversHO1.M81B3C74nkmtbh
ieplmniamscgsmtoumtsreestACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra-MSC GSMUMTS handoversHO1.M81B3C73nkmtbh
iniemscgsmtoumtsclearACCUMULATIONINT8Number of calls dropped due to failed inter-MSC GSM-UMTS handoversHO1.M81B3C82nkmtbh
inieplmngsmtoumtsclearACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN inter-MSC GSMUMTS handoversHO1.M81B3C98nkmtbh
INTRA_MSS_C_GSM_NB_TO_UMTS_NBACCUMULATIONINT8The number of successful handovers from GSM to UMTS where codec changed from narrowband to narrowband.HO1.M81B3C201nkmtbh
INTRA_MSS_C_GSM_NB_TO_UMTS_WBACCUMULATIONINT8The number of successful handovers from GSM to UMTS where codec changed from narrowband to wideband.HO1.M81B3C202nkmtbh
outiemscgsmtoumtsclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC GSM-UMTS handoversHO1.M81B3C90nkmtbh
outiemscgsmtoumtsreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC GSM-UMTS handoversHO1.M81B3C89nkmtbh
outieplmngsmtoumtsclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN inter-MSC GSMUMTS handoversHO1.M81B3C106nkmtbh
outieplmngsmtoumtsreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter- PLMN inter-MSC GSM-UMTS handoversHO1.M81B3C105nkmtbh
succ_i_msc_gsm_umts_hoACCUMULATIONINT8The number of successful intra-MSC GSM-UMTS handovers. HO1.M81B3C7nkmtbh
succ_inc_e_msc_gsm_umts_hoACCUMULATIONINT8The number of successful incoming inter-MSC GSM-UMTS handovers. HO1.M81B3C17nkmtbh
succ_inc_e_plmn_gsm_umts_hoACCUMULATIONINT8The number of successful incoming inter-PLMN GSM-UMTS handovers. HO1.M81B3C35nkmtbh
succ_out_e_msc_gsm_umts_hoACCUMULATIONINT8The number of successful outgoing inter-MSC GSM-UMTS handovers. HO1.M81B3C27nkmtbh
succ_out_e_plmn_gsm_umts_hoACCUMULATIONINT8The number of successful outgoing inter-PLMN GSM-UMTS handovers. HO1.M81B3C43nkmtbh
succ_plmn_msc_gsm_umts_hoACCUMULATIONINT8The number of successful inter- PLMN intra-MSC GSM-UMTS handovers. HO1.M81B3C51nkmtbh
unsucc_i_msc_gsm_umts_hoACCUMULATIONINT8The number of unsuccessful intra-MSC GSM-UMTS handovers. HO1.M81B3C8nkmtbh
unsucc_inc_e_msc_gsm_umts_hoACCUMULATIONINT8The number of unsuccessful incoming inter-MSC GSM-UMTS handovers. HO1.M81B3C18nkmtbh
unsucc_inc_e_plmn_gsm_umts_hoACCUMULATIONINT8The number of unsuccessful incoming inter-PLMN GSM-UMTS handovers. HO1.M81B3C36nkmtbh
unsucc_out_e_msc_gsm_umts_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-MSC GSM-UMTS handovers. HO1.M81B3C28nkmtbh
unsucc_out_e_plmn_gsm_umts_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-PLMN GSM-UMTS handovers. HO1.M81B3C44nkmtbh
unsucc_plmn_msc_gsm_umts_hoACCUMULATIONINT8The number of unsuccessful inter- PLMN intra-MSC GSM-UMTS handovers. HO1.M81B3C52nkmtbh


MSC.Nokia.GSM.Handover

This measurement contains the information about the number of the MSC and BSC controlled successful and unsuccessful handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_succ_ho_totalPERCENTAGEFLOATPercentage successful handoverspercentok({succ_ho_total}, ({succ_ho_total} + {unsucc_ho_total}))nkmtbh
%_succ_re_etab_hoPERCENTAGEFLOATPercentage successful re-establishment handovers.percentok({succ_re_etab_ho}, ({succ_re_etab_ho} + {unsucc_re_etab_ho}))nkmtbh
%_unsucc_ho_totalPERCENTAGEFLOATPercentage unsuccessful handoverspercentfail({unsucc_ho_total}, ({succ_ho_total} + {unsucc_ho_total}))nkmtbh
%_unsucc_re_etab_hoPERCENTAGEFLOATPercentage unsuccessful re-establishment handovers.percentfail({unsucc_re_etab_ho}, ({succ_re_etab_ho} + {unsucc_re_etab_ho}))nkmtbh
intrarncokACCUMULATIONINT8Number of successful intra-RNC handovers.HO1.M81B3C61nkmtbh
succ_ho_totalACCUMULATIONINT8The total number of successful handovers HO1.M81B3C25nkmtbh
succ_i_cell_hoACCUMULATIONINT8The number of successful intra-cell handovers. HO1.M81B3C1nkmtbh
succ_intra_bsc_hoACCUMULATIONINT8The number of successful intra-BSC handovers.HO1.M81B3C3nkmtbh
succ_re_etab_hoACCUMULATIONINT8The number of successful re-establishment handovers.HO1.M81B3C11nkmtbh
succsubseqintermsctomscanokACCUMULATIONINT8Number of unsuccessful subsequent inter-MSC handovers which are handled back to the first MSC. This counter is updated only in MSC-A (anchor MSC).HO1.M81B3C58nkmtbh
succsubseqintermsctomscaokACCUMULATIONINT8Number of successful subsequent inter-MSC handovers which are handled back to the first MSC. This counter is updated only in MSC-A (anchor MSC).HO1.M81B3C57nkmtbh
succsubseqintermsctomsccnokACCUMULATIONINT8Number of unsuccessful subsequent inter-MSC handovers which are handled towards to a third MSC. This counter is updated only in MSC-A (anchor MSC).HO1.M81B3C60nkmtbh
succsubseqintermsctomsccokACCUMULATIONINT8Number of successful subsequent inter- MSC handovers which are handled towards to a third MSC. This counter is updated only in MSC-A (anchor MSC).HO1.M81B3C59nkmtbh
totalhoclearACCUMULATIONINT8Total number of calls dropped due to failed handoversHO1.M81B3C112nkmtbh
totalhoreestACCUMULATIONINT8Total number of successful reestablishments in failed handoversHO1.M81B3C111nkmtbh
unsucc_ho_totalACCUMULATIONINT8The total number of unsuccessful handovers HO1.M81B3C26nkmtbh
unsucc_re_etab_hoACCUMULATIONINT8The number of unsuccessful re-establishment handovers.HO1.M81B3C12nkmtbh


MSC.Nokia.GSM.Integrated_Announcement_Device

This measurement contains the measurement results of the integrated announcement device. N.B. There is a secondary key of announcement_device.

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
nbr_calls_annACCUMULATIONINT8The number of announcement attemptsANN.M26B2C2nkmtbh
nbr_lost_calls_annACCUMULATIONINT8The number of lost calls.ANN.M26B2C3nkmtbh
tot_listening_timeACCUMULATIONINT8The total listening time.ANN.M26B2C4nkmtbh
vanid_invalid_recordINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid.ANN.M26B2C5nkmtbh


MSC.Nokia.GSM.Intra_GSM_Handovers

This measurement contains the information about the number of the MSC and BSC controlled successful and unsuccessful handovers. Specifically Intra GSM.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_intramscintragsmnokPERCENTAGEFLOATPercentage unsuccessful intra-MSC intra-GSM handoverspercentfail({intramscintragsmnok}, ({intramscintragsmok} + {intramscintragsmnok}))nkmtbh
%_intramscintragsmokPERCENTAGEFLOATPercentage successful intra-MSC intra-GSM handoverspercentok({intramscintragsmok}, ({intramscintragsmok} + {intramscintragsmnok}))nkmtbh
%_succ_inc_e_msc_i_gsm_hoPERCENTAGEFLOATPercentage successful incoming inter-MSC intra-GSM handovers.percentok({succ_inc_e_msc_i_gsm_ho}, ({succ_inc_e_msc_i_gsm_ho} + {unsucc_inc_e_msc_i_gsm_ho}))nkmtbh
%_succ_inc_e_plmn_i_gsm_hoPERCENTAGEFLOATPercentage successful incoming inter-PLMN intra-GSM handovers.percentok({succ_inc_e_plmn_i_gsm_ho}, ({succ_inc_e_plmn_i_gsm_ho} + {unsucc_inc_e_plmn_i_gsm_ho}))nkmtbh
%_succ_out_e_msc_i_gsm_hoPERCENTAGEFLOATPercentage successful outgoing inter-MSC intra-GSM handovers.percentok({succ_out_e_msc_i_gsm_ho}, ({succ_out_e_msc_i_gsm_ho} + {unsucc_out_e_msc_i_gsm_ho}))nkmtbh
%_succ_out_e_plmn_i_gsm_hoPERCENTAGEFLOATPercentage successful outgoing inter-PLMN intra-GSM handovers.percentok({succ_out_e_plmn_i_gsm_ho}, ({succ_out_e_plmn_i_gsm_ho} + {unsucc_out_e_plmn_i_gsm_ho}))nkmtbh
%_succ_plmn_msc_gsm_hoPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC intra-GSM handovers.percentok({succ_plmn_msc_gsm_ho}, ({succ_plmn_msc_gsm_ho} + {unsucc_plmn_msc_gsm_ho}))nkmtbh
%_unsucc_inc_e_msc_i_gsm_hoPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC intra-GSM handovers.percentfail({unsucc_inc_e_msc_i_gsm_ho}, ({succ_inc_e_msc_i_gsm_ho} + {unsucc_inc_e_msc_i_gsm_ho}))nkmtbh
%_unsucc_inc_e_plmn_i_gsm_hoPERCENTAGEFLOATPercentage unsuccessful incoming inter-PLMN intra-GSM handovers.percentfail({unsucc_inc_e_plmn_i_gsm_ho}, ({succ_inc_e_plmn_i_gsm_ho} + {unsucc_inc_e_plmn_i_gsm_ho}))nkmtbh
%_unsucc_out_e_msc_i_gsm_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC intra-GSM handoverspercentfail({unsucc_out_e_msc_i_gsm_ho}, ({succ_out_e_msc_i_gsm_ho} + {unsucc_out_e_msc_i_gsm_ho}))nkmtbh
%_unsucc_out_e_plmn_i_gsm_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN intra-GSM handovers.percentfail({unsucc_out_e_plmn_i_gsm_ho}, ({succ_out_e_plmn_i_gsm_ho} + {unsucc_out_e_plmn_i_gsm_ho}))nkmtbh
%_unsucc_plmn_msc_gsm_hoPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC intra-GSM handovers.percentfail({unsucc_plmn_msc_gsm_ho}, ({succ_plmn_msc_gsm_ho} + {unsucc_plmn_msc_gsm_ho}))nkmtbh
dropped_callsACCUMULATIONINT8Number of calls dropped.{iamsciagsmclear} + {ieplmniamsciagsmclear} + {iniemsciagsmclear} + {outiemsciagsmclear} + {inieplmniagsmclear} + {outieplmniagsmclear}nkmtbh
iamsciagsmclearACCUMULATIONINT8Number of calls dropped due to failed intra-MSC intra-GSM handoversHO1.M81B3C64nkmtbh
iamsciagsmreestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC intra-GSM handoversHO1.M81B3C63nkmtbh
ieplmniamsciagsmclearACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC intra-GSM handoversHO1.M81B3C72nkmtbh
ieplmniamsciagsmreestACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra-MSC intra-GSM handoversHO1.M81B3C71nkmtbh
iniemsciagsmclearACCUMULATIONINT8Number of calls dropped due to failed inter-MSC intra-GSM handoversHO1.M81B3C80nkmtbh
inieplmniagsmclearACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN inter-MSC intra- GSM handoversHO1.M81B3C96nkmtbh
intramscintragsmnokACCUMULATIONINT8Number of unsuccessful intra-MSC intra-GSM handoversHO1.M81B3C6nkmtbh
intramscintragsmokACCUMULATIONINT8Number of successful intra-MSC intra-GSM handoversHO1.M81B3C5nkmtbh
outiemsciagsmclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC intra-GSM handoversHO1.M81B3C88nkmtbh
outiemsciagsmreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC intra-GSM handoversHO1.M81B3C87nkmtbh
outieplmniagsmclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN inter-MSC intra- GSM handoversHO1.M81B3C104nkmtbh
outieplmniagsmreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN inter-MSC intra-GSM handoversHO1.M81B3C103nkmtbh
succ_inc_e_msc_i_gsm_hoACCUMULATIONINT8The number of successful incoming inter-MSC intra-GSM handovers. HO1.M81B3C15nkmtbh
succ_inc_e_plmn_i_gsm_hoACCUMULATIONINT8The number of successful incoming inter-PLMN intra-GSM handovers. HO1.M81B3C33nkmtbh
succ_out_e_msc_i_gsm_hoACCUMULATIONINT8The number of successful outgoing inter-MSC intra-GSM handovers. HO1.M81B3C23nkmtbh
succ_out_e_plmn_i_gsm_hoACCUMULATIONINT8The number of successful outgoing inter-PLMN intra-GSM handovers. HO1.M81B3C41nkmtbh
succ_plmn_msc_gsm_hoACCUMULATIONINT8The number of successful inter- PLMN intra-MSC intra-GSM handovers. HO1.M81B3C49nkmtbh
unsucc_inc_e_msc_i_gsm_hoACCUMULATIONINT8The number of unsuccessful incoming inter-MSC intra-GSM handovers. HO1.M81B3C16nkmtbh
unsucc_inc_e_plmn_i_gsm_hoACCUMULATIONINT8The number of unsuccessful incoming inter-PLMN intra-GSM handovers. HO1.M81B3C34nkmtbh
unsucc_out_e_msc_i_gsm_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-MSC intra-GSM handovers. HO1.M81B3C24nkmtbh
unsucc_out_e_plmn_i_gsm_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-PLMN intra-GSM handovers. HO1.M81B3C42nkmtbh
unsucc_plmn_msc_gsm_hoACCUMULATIONINT8The number of unsuccessful inter- PLMN intra-MSC intra-GSM handovers. HO1.M81B3C50nkmtbh


MSC.Nokia.GSM.Intra_UMTS_Handovers

This measurement contains the information about the number of the MSC and BSC controlled successful and unsuccessful handovers. Specifically Intra UMTS

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_succ_i_msc_i_umts_hoPERCENTAGEFLOATPercentage successful intra-MSC intra-UMTS handovers.percentok({succ_i_msc_i_umts_ho}, ({succ_i_msc_i_umts_ho} + {unsucc_i_msc_i_umts_ho}))nkmtbh
%_succ_inc_e_msc_i_umts_hoPERCENTAGEFLOATPercentage successful incoming inter-MSC intra-UMTS handovers.percentok({succ_inc_e_msc_i_umts_ho}, ({succ_inc_e_msc_i_umts_ho} + {unsucc_inc_e_msc_i_umts_ho}))nkmtbh
%_succ_inc_e_plmn_i_umts_hoPERCENTAGEFLOATPercentage successful inter-PLMN intra-UMTS handovers.percentok({succ_inc_e_plmn_i_umts_ho}, ({succ_inc_e_plmn_i_umts_ho} + {unsucc_inc_e_plmn_i_umts_ho}))nkmtbh
%_succ_out_e_msc_i_umts_hoPERCENTAGEFLOATPercentage successful outgoing inter-MSC intra-UMTS handovers.percentok({succ_out_e_msc_i_umts_ho}, ({succ_out_e_msc_i_umts_ho} + {unsucc_out_e_msc_i_umts_ho}))nkmtbh
%_succ_out_e_plmn_i_umts_hoPERCENTAGEFLOATPercentage successful outgoing inter-PLMN intra-UMTS handovers.percentok({succ_out_e_plmn_i_umts_ho}, ({succ_out_e_plmn_i_umts_ho} + {unsucc_out_e_plmn_i_umts_ho}))nkmtbh
%_succ_plmn_msc_umts_hoPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC intra-UMTS handovers.percentok({succ_plmn_msc_umts_ho}, ({succ_plmn_msc_umts_ho} + {unsucc_plmn_msc_umts_ho}))nkmtbh
%_unsucc_i_msc_i_umts_hoPERCENTAGEFLOATPercentage unsuccessful intra-MSC intra-UMTS handovers.percentfail({unsucc_i_msc_i_umts_ho}, ({succ_i_msc_i_umts_ho} + {unsucc_i_msc_i_umts_ho}))nkmtbh
%_unsucc_inc_e_msc_i_umts_hoPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC intra-UMTS handovers.percentfail({unsucc_inc_e_msc_i_umts_ho}, ({succ_inc_e_msc_i_umts_ho} + {unsucc_inc_e_msc_i_umts_ho}))nkmtbh
%_unsucc_inc_e_plmn_i_umts_hoPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-UMTS handovers.percentfail({unsucc_inc_e_plmn_i_umts_ho}, ({succ_inc_e_plmn_i_umts_ho} + {unsucc_inc_e_plmn_i_umts_ho}))nkmtbh
%_unsucc_out_e_msc_i_umts_hoPERCENTAGEFLOATPercentage unsuccesful outgoing inter-MSC intra-UMTS handovers.percentfail({unsucc_out_e_msc_i_umts_ho}, ({succ_out_e_msc_i_umts_ho} + {unsucc_out_e_msc_i_umts_ho}))nkmtbh
%_unsucc_out_e_plmn_i_umts_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN intra-UMTS handovers.percentfail({unsucc_out_e_plmn_i_umts_ho}, ({succ_out_e_plmn_i_umts_ho} + {unsucc_out_e_plmn_i_umts_ho}))nkmtbh
%_unsucc_plmn_msc_umts_hoPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC intra-UMTS handovers.percentfail({unsucc_plmn_msc_umts_ho}, ({succ_plmn_msc_umts_ho} + {unsucc_plmn_msc_umts_ho}))nkmtbh
dropped_callsACCUMULATIONINT8Number of dropped calls{iamsciaumtsclear} + {ieplmniamsciaumtsclear} + {iniemsciaumtsclear} + {outiemsciaumtsclear} + {inieplmniaumtsclear} + {outieplmniaumtsclear}nkmtbh
iamsciaumtsclearACCUMULATIONINT8Number of calls dropped due to failed intra-MSC intra-UMTS handoversHO1.M81B3C70nkmtbh
iamsciaumtsreestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC intra-UMTS handoversHO1.M81B3C68nkmtbh
ieplmniamsciagsmreestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC intra-UMTS handoversHO1.M81B3C69nkmtbh
ieplmniamsciaumtsclearACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC intra-UMTS handoversHO1.M81B3C78nkmtbh
ieplmniamsciaumtsreestACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra-MSC intra- UMTS handoversHO1.M81B3C77nkmtbh
iniemsciaumtsclearACCUMULATIONINT8Number of calls dropped due to failed inter-MSC intra-UMTS handoversHO1.M81B3C86nkmtbh
inieplmniaumtsclearACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN inter-MSC intra- UMTS handoversHO1.M81B3C102nkmtbh
INTRA_MSS_C_UMTS_NB_TO_UMTS_NBACCUMULATIONINT8The number of successful handovers from UMTS to UMTS where codec changed from narrowband to narrowband.HO1.M81B3C203nkmtbh
INTRA_MSS_C_UMTS_NB_TO_UMTS_WBACCUMULATIONINT8The number of successful handovers from UMTS to UMTS where codec changed from narrowband to wideband.HO1.M81B3C204nkmtbh
INTRA_MSS_C_UMTS_WB_TO_UMTS_NBACCUMULATIONINT8The number of successful handovers from UMTS to UMTS where codec changed from wideband to narrowband.HO1.M81B3C205nkmtbh
INTRA_MSS_C_UMTS_WB_TO_UMTS_WBACCUMULATIONINT8The number of successful handovers from UMTS to UMTS where codec changed from wideband to wideband.HO1.M81B3C206nkmtbh
outiemsciaumtsclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC intra-UMTS handoversHO1.M81B3C94nkmtbh
outiemsciaumtsreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC intra-UMTS handoversHO1.M81B3C93nkmtbh
outieplmniaumtsclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN inter-MSC intra- UMTS handoversHO1.M81B3C110nkmtbh
outieplmniaumtsreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN inter-MSC intra-UMTS handoversHO1.M81B3C109nkmtbh
succ_i_msc_i_umts_hoACCUMULATIONINT8The number of successful intra-MSC intra-UMTS handovers. HO1.M81B3C13nkmtbh
succ_inc_e_msc_i_umts_hoACCUMULATIONINT8The number of successful incoming inter-MSC intra-UMTS handovers. HO1.M81B3C21nkmtbh
succ_inc_e_plmn_i_umts_hoACCUMULATIONINT8The number of successful incoming inter-PLMN intra-UMTS handovers. HO1.M81B3C39nkmtbh
succ_out_e_msc_i_umts_hoACCUMULATIONINT8The number of successful outgoing inter-MSC intra-UMTS handovers. HO1.M81B3C31nkmtbh
succ_out_e_plmn_i_umts_hoACCUMULATIONINT8The number of successful outgoing inter-PLMN intra-UMTS handovers. HO1.M81B3C47nkmtbh
succ_plmn_msc_umts_hoACCUMULATIONINT8The number of successful inter- PLMN intra-MSC intra-UMTS handovers. HO1.M81B3C55nkmtbh
unsucc_i_msc_i_umts_hoACCUMULATIONINT8The number of unsuccessful intra-MSC intra-UMTS handovers. HO1.M81B3C14nkmtbh
unsucc_inc_e_msc_i_umts_hoACCUMULATIONINT8The number of unsuccessful incoming inter-MSC intra-UMTS handovers. HO1.M81B3C22nkmtbh
unsucc_inc_e_plmn_i_umts_hoACCUMULATIONINT8The number of unsuccessful incoming inter-PLMN intra-UMTS handovers. HO1.M81B3C40nkmtbh
unsucc_out_e_msc_i_umts_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-MSC intra-UMTS handovers. HO1.M81B3C32nkmtbh
unsucc_out_e_plmn_i_umts_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-PLMN intra-UMTS handovers. HO1.M81B3C48nkmtbh
unsucc_plmn_msc_umts_hoACCUMULATIONINT8The number of unsuccessful inter- PLMN intra-MSC intra-UMTS handovers. HO1.M81B3C56nkmtbh


MSC.Nokia.GSM.IWF_Calltype

The IWF measurement measures the usage of the IWF capacity and radio resources in data calls. N.B. There is a secondary key of call_type

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
iwf_calltype_answACCUMULATIONINT8Number of call attempts (0...999999) that have been answered. CODING: DWIWFCT.M311B2C2nkmtbh
iwf_calltype_callsACCUMULATIONINT8Number of call attempts (0...999999) that have ended in the measurement period. CODING: DWIWFCT.M311B2C1nkmtbh
iwf_calltype_failACCUMULATIONINT8Number of failed call attempts where the failure has been in IWF. CODING: DWIWFCT.M311B2C3nkmtbh
iwf_calltype_onlineACCUMULATIONINT8Number of successful synchronisations between data terminals (0...999999). This counter indicates the amount of connections where the user data may have been transmitted. CODING: DWIWFCT.M311B2C4nkmtbh
iwf_calltype_seizureERLANGFLOATTraffic intensity (0.0...999999.9) is the amount of total reservation time divided by the length of the measurement period. Total reservation time is measured in seconds from the reservation and the release of internal data circuits by call type.IWFCT.M311B2C5nkmtbh


MSC.Nokia.GSM.LAN_Ethernet_Msg_Bus

LAN Ethernet Message Bus report

KPITypeData TypeDescriptionDerivationAdditional Summaries
LANEMBGEN_ERROR_DATABASEACCUMULATIONINT8Database error.MLANEMB.M293B3C1nkmtbh
LANEMBGEN_ERROR_PROVIDERACCUMULATIONINT8The creation of hand process has failed.MLANEMB.M293B3C2nkmtbh


MSC.Nokia.GSM.LAPD_Error

This section describes the key columns and counters of M223

KPITypeData TypeDescriptionDerivationAdditional Summaries
n201_errACCUMULATIONINT8N201 error (cntr O)LAPEMSCR.M223B2C15nkmtbh
nr_errACCUMULATIONINT8N(R) error (cntr J)LAPEMSCR.M223B2C14nkmtbh
peer_init_re_estabACCUMULATIONINT8Peer initiated re-establishment (cntr F)LAPEMSCR.M223B2C13nkmtbh
rec_frame_wrong_sizeACCUMULATIONINT8Receipt of frame with wrong size (cntr N)LAPEMSCR.M223B2C12nkmtbh
rec_frmr_respACCUMULATIONINT8Receipt of FRMR response (cntr K)LAPEMSCR.M223B2C9nkmtbh
rec_i_field_not_permACCUMULATIONINT8Receipt of I field not permitted (cntr M)LAPEMSCR.M223B2C11nkmtbh
rec_non_impl_frameACCUMULATIONINT8Receipt of non-implemented frame (cntr L)LAPEMSCR.M223B2C10nkmtbh
rec_uncon_dm_f0ACCUMULATIONINT8Receipt of unsolicited DM, F=0 (cntr E)LAPEMSCR.M223B2C1nkmtbh
rec_uncon_dm_f1ACCUMULATIONINT8Receipt of unsolicited DM, F=1 (cntr B)LAPEMSCR.M223B2C2nkmtbh
rec_uncon_rr_rnr_rej_f1ACCUMULATIONINT8Receipt of unsolicited RR/RNR/REJ, F=1 (cntr A)LAPEMSCR.M223B2C5nkmtbh
rec_uncon_ua_f0ACCUMULATIONINT8Receipt of unsolicited UA, F=0 (cntr D)LAPEMSCR.M223B2C3nkmtbh
rec_uncon_ua_f1ACCUMULATIONINT8Receipt of unsolicited UA, F=1 (cntr C)LAPEMSCR.M223B2C4nkmtbh
unsuc_retrans_discACCUMULATIONINT8Unsuccessful retransmission of DISC (cntr H)LAPEMSCR.M223B2C7nkmtbh
unsuc_retrans_sabmeACCUMULATIONINT8Unsuccessful retransmission of SABME (cntr G)LAPEMSCR.M223B2C6nkmtbh
unsuc_retrans_stat_enqACCUMULATIONINT8Unsuccessful retransmission of status inquiry (cntr I)LAPEMSCR.M223B2C8nkmtbh


MSC.Nokia.GSM.LAPD_Traffic

This section describes the key columns and counters of M221

KPITypeData TypeDescriptionDerivationAdditional Summaries
i_frame_oct_recACCUMULATIONINT8Received I frame octetsLAPDMSCR.M221B2C6nkmtbh, nkmttbh
i_frame_oct_transACCUMULATIONINT8Transmitted I frame octetsLAPDMSCR.M221B2C5nkmtbh, nkmttbh
i_frames_recACCUMULATIONINT8Received I framesLAPDMSCR.M221B2C2nkmtbh, nkmttbh
i_frames_transACCUMULATIONINT8Transmitted I framesLAPDMSCR.M221B2C1nkmtbh, nkmttbh
tot_oct_recACCUMULATIONINT8Received total octet countLAPDMSCR.M221B2C10nkmtbh, nkmttbh
tot_oct_transACCUMULATIONINT8Transmitted total octet countLAPDMSCR.M221B2C9nkmtbh, nkmttbh
ui_frame_oct_recACCUMULATIONINT8Received UI frame octetsLAPDMSCR.M221B2C8nkmtbh, nkmttbh
ui_frame_oct_transACCUMULATIONINT8Transmitted UI frame octetsLAPDMSCR.M221B2C7nkmtbh, nkmttbh
ui_frames_recACCUMULATIONINT8Received UI framesLAPDMSCR.M221B2C4nkmtbh, nkmttbh
ui_frames_transACCUMULATIONINT8Transmitted UI framesLAPDMSCR.M221B2C3nkmtbh, nkmttbh


MSC.Nokia.GSM.LAPD_Utilisation

This section describes the key columns and counters of M222

KPITypeData TypeDescriptionDerivationAdditional Summaries
clock_sgn_missACCUMULATIONINT8Clock signal missingLAPUMSCR.M222B2C11nkmtbh
crc_errACCUMULATIONINT8CRC errorsLAPUMSCR.M222B2C5nkmtbh
dl_data_indACCUMULATIONINT8Number of DL-DATA-INDICATIONSLAPUMSCR.M222B2C2nkmtbh
dl_data_req_delACCUMULATIONINT8Deleted DL-DATA-REQUESTSLAPUMSCR.M222B2C7nkmtbh
dl_data_reqACCUMULATIONINT8Number of DL-DATA-REQUESTSLAPUMSCR.M222B2C1nkmtbh
dl_unit_data_indACCUMULATIONINT8Number of DL-UNIT-DATA-INDICATIONSLAPUMSCR.M222B2C4nkmtbh
dl_unit_data_reqACCUMULATIONINT8Number of DL-UNIT-DATA-REQUESTSLAPUMSCR.M222B2C3nkmtbh
dmc_msg_buff_overflACCUMULATIONINT8DMC message buffer overflowsLAPUMSCR.M222B2C10nkmtbh
frame_errACCUMULATIONINT8Frame errorsLAPUMSCR.M222B2C6nkmtbh
i_frames_delACCUMULATIONINT8Deleted I frames in windowLAPUMSCR.M222B2C8nkmtbh
t200_expACCUMULATIONINT8T200 expiriesLAPUMSCR.M222B2C9nkmtbh


MSC.Nokia.GSM.MSC_Signalling_Pt_Traffic_User

Signalling traffic measurements

The performance data measurements for this KPI group are recorded against the combination of MSC, SIO (sio_id) and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8The number of SIF and SIO received with the given SIO.UTRAMSC.M214B2C1 
sif_sio_transACCUMULATIONINT8The number of SIF and SIO transmitted with the given SIO.UTRAMSC.M214B2C2 


MSC.Nokia.GSM.MSC_UPD

The UPD to Number Destination measurement shows the number and type of calls or call attempts received in each UPD and a number destination during the results accumulation period. N.B. There is a secondary key of UPD

The performance data measurements for this KPI group are recorded against the combination of MSC, Destination_Type (destination_type_id) and UPD (upd_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_nupd_successful_callsPERCENTAGEFLOATPercentage successful calls.percentok({nupd_successful_calls}, {nupd_num_of_call_att})nkmtbh
nupd_answered_callsACCUMULATIONINT8The number of calls (0...999999) that have reached the conversation state. The field is updated when the first released circuit is released.NUPD.M385B2C6nkmtbh
nupd_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when the data provider in the signalling unit or the signalling unit(s) is restarted during the period and data might not be reliable.NUPD.M385B2C14nkmtbh
nupd_erlangs_x100ERLANGFLOATThe amount of traffic from a circuit group to a number destination in erlangs (0.0...9999.9). That means the total reservation time of the measured object in relation to the results accumulation period. The erlang calculation starts when both circuits are seized. The end point of erlang calculation is determined by the circuit that is released first. All of the circuit reservation time is updated in the results accumulation period in which the first released circuit is released. For this reason remarkably large values in the ERLANGS field are possible if there are many calls that have started before the results accumulation period but that end in the results accumulation period.NUPD.M385B2C10nkmtbh
nupd_errorsACCUMULATIONINT8Number of NUPD errors{nupd_subsc_error} + {nupd_int_error} + {nupd_ext_error}nkmtbh
nupd_ext_errorACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in an error in the trunk circuit, clear codes 800...BFF. The field is updated when the first released circuit is released.NUPD.M385B2C9nkmtbh
nupd_int_errorACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in an error in the home exchange, clear codes 400...7FF. The field is updated when the first released circuit is released.NUPD.M385B2C8nkmtbh
nupd_num_of_call_attACCUMULATIONINT8Number of call attempts (0...999999). The field is updated when the first released circuit is released.NUPD.M385B2C4nkmtbh
nupd_overload_ctrl_actINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 10 when the Automatic Overload Control of Statistics feature has been activated.NUPD.M385B2C13nkmtbh
nupd_subsc_errorACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the first released circuit is released. NUPD.M385B2C7nkmtbh
nupd_successful_callsACCUMULATIONINT8Number of successful call attempts (0...999999), clear codes 0...3FF. The field is updated when the first released circuit is released.NUPD.M385B2C5nkmtbh


MSC.Nokia.GSM.Number_Destination

This measurement contains the measurement results from the number destination measurements.N.B. There is a secondary key of number_destination

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_answered_callsPERCENTAGEFLOATPercentage of calls that were answeredpercentok({ans_calls}, {nbr_calls})nkmtbh
ans_callsACCUMULATIONINT8Answered calls.NUMD.M17B2C7nkmtbh
avr_traf_erlangERLANGFLOATThe average traffic in erlangsNUMD.M17B2C11nkmtbh
ext_err_callsACCUMULATIONINT8Calls ended in the external error condition.NUMD.M17B2C10nkmtbh
int_err_callsACCUMULATIONINT8Calls ended in the internal error condition.NUMD.M17B2C9nkmtbh
nbr_callsACCUMULATIONINT8The number of calls made.NUMD.M17B2C4nkmtbh
numdest_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when data provider in signalling unit or signalling unit(s) is restarted during the period and data might not be reliable.NUMD.M17B2C14nkmtbh
numdest_invalid_rec_foundINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid.NUMD.M17B2C12nkmtbh
numdest_overload_ctrl_actINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 10 when the Automatic Overload Control of Statistics feature has been activated.NUMD.M17B2C13nkmtbh
subsc_errACCUMULATIONINT8The number of subscriber errors.NUMD.M17B2C8nkmtbh
succ_callsACCUMULATIONINT8The number of successful calls.NUMD.M17B2C5nkmtbh


MSC.Nokia.GSM.Paging_LAC

This section describes the key columns and counters of M353

KPITypeData TypeDescriptionDerivationAdditional Summaries
answer_timeINTENSITYFLOATThe average time between the last paging request message and the corresponding paging response (during a paging) is shown in the ANS.TIME field in tenth of second. If there is not any successful paging this counter is not applicable.MSCPPL.M353B3C7nkmtbh
datamissing_in_paging_per_laINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, that is, only a subset of the data could be collected. It means that the printed counters per LAC are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)MSCPPL.M353B2C1nkmtbh
paging_attempt_perlaACCUMULATIONINT8Number of initiated pagings from the VLR to the specific LA. This counter contains the paging of both Normal and telemeteric subscribers. Searchings, PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.MSCPPL.M353B3C1nkmtbh
paging_attempt_with_imsifailACCUMULATIONINT8The number of paging attempt with IMSI for failed pagings (ATT#(FAIL)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging failed. This counter contains the paging of both Normal and telemeteric subscribers. Searchings, PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.MSCPPL.M353B3C5nkmtbh
paging_attempt_with_imsisuccACCUMULATIONINT8The number of paging attempt with IMSI for successful pagings (ATT#(SUCC)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging was successful. This counter contains the paging of both Normal and telemeteric subscribers. Searchings, PS domain pagings are not included in thiscounter. This counter is not updated when the subscriber is busy during the paging.MSCPPL.M353B3C3nkmtbh
paging_attempt_with_tmsifailACCUMULATIONINT8The number of paging attempt with TMSI for failed pagings (ATT#(FAIL)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging failed. This counter contains the paging of both Normal and telemeteric subscribers. Searchings, PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.MSCPPL.M353B3C6nkmtbh
paging_attempt_with_tmsisuccACCUMULATIONINT8The number of paging attempt with TMSI for successful pagings (ATT#(SUCC)) counters show how many paging requests were sent to the A and Iu interfaces (from MSC) per LAC when the paging was successful. This counter contains the paging of both Normal and telemeteric subscribers. Searchings, PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.MSCPPL.M353B3C4nkmtbh
paging_succ_perlaACCUMULATIONINT8Number of successful pagings in VLR in the specific LA. This counter contains the paging of both Normal and telemeteric subscribers. Searchings, PS domain pagings are not included in this counter. This counter is not updated when the subscriber is busy during the paging.MSCPPL.M353B3C2nkmtbh


MSC.Nokia.GSM.Priority_calls

Priority call data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
default_priority_callsACCUMULATIONINT8Total number of incoming PRIORITY calls without the Precedence parameter (CPC=PRIORITY Call, ISUP/BICC MLPP field is not filled). This counter is updated in the VMSC in MT call case (counter 0.8).PRCA.M392B2C9nkmtbh
gets_call_requestsACCUMULATIONINT8Total number of MO GETS call requests (CPC=PRIORITY Call, but eMLPP is not used) (counter 0.3).PRCA.M392B2C4nkmtbh
inc_nsep_callsACCUMULATIONINT8Total number of PRIORITY calls received on incoming trunks (counter 0.5).PRCA.M392B2C6nkmtbh
inc_nsep_mt_callsACCUMULATIONINT8The total number of PRIORITY calls received on incoming trunks whose destination is an MS served by that MSC/VLR (counter 0.4).PRCA.M392B2C5nkmtbh
nsep_abandonACCUMULATIONINT8The total number of times when the PRIORITY calls are removed from a trunk queue because the MS has disconnected the call, radio contact with the MS has been lost, or a release message is received on the incoming ISUP trunk (counter 0.16).PRCA.M392B3C9nkmtbh
nsep_attemptsACCUMULATIONINT8Requires trunks to point outside the MSC (counter 0.10).PRCA.M392B3C3nkmtbh
nsep_callsACCUMULATIONINT8Shows which trunks are successfully set up to a succeeding MSC, that is, an ACM, ANM, or REL message (for an ISUP trunk), or an acknowledgement wink (for an MF trunk) is received (counter 0.11).PRCA.M392B3C4nkmtbh
nsep_channel_assignedACCUMULATIONINT8Total number of incoming PRIORITY calls for which radio traffic channel has been assigned (counter 0.6).PRCA.M392B2C7nkmtbh
nsep_no_circACCUMULATIONINT8These are the calls that cannot be routed on any trunk to point outside the MSC because no idle trunks are available (counter 0.12).PRCA.M392B3C5nkmtbh
nsep_overflowACCUMULATIONINT8The total number of times that the PRIORITY calls fail to queue for a trunk in a trunk group because the maximum trunk queue length for that trunk group has been reached (counter 0.14).PRCA.M392B3C7nkmtbh
nsep_queuedACCUMULATIONINT8The total number of PRIORITY calls that are queued for a trunk to point outside the MSC (counter 0.13).PRCA.M392B3C6nkmtbh
nsep_time_outACCUMULATIONINT8The total number of times when the PRIORITY calls are removed from a trunk queue because the call exceeded the maximum trunk queue time for that trunk group (counter 0.15).PRCA.M392B3C8nkmtbh
PRIO_3G2G_DRH_ATTACCUMULATIONINT8Total number of priority call terminations for which Directed Retry Handover to the GSM network has been attempted.PRCA.M392B5C4nkmtbh
PRIO_3G2G_DRH_SUCCACCUMULATIONINT8Total number of priority call terminations for which Directed Retry Handover to the GSM network was successful.PRCA.M392B5C5nkmtbh
PRIO_3G2G_DRHDRH_TRK_TIMEOUTACCUMULATIONINT8Total number of priority call terminations for which trunk queuing for Directed Retry Handover has timed out.PRCA.M392B5C6nkmtbh
term_nsep_callsACCUMULATIONINT8Total number of PRIORITY calls whose destination is an MS served by that MSC/VLR. This counter is regardless of the origin of calls, for example, it is updated in the case of a mobile-originating, PSTNoriginating call (counter 0.7).PRCA.M392B2C8nkmtbh
WPS_3G2G_DRH_ATTACCUMULATIONINT8Total number of WPS call invocations for which Directed Retry Handover to the GSM network has been attempted.PRCA.M392B5C1nkmtbh
WPS_3G2G_DRH_SUCCACCUMULATIONINT8Total number of WPS call invocations for which Directed Retry Handover to the GSM network was successful.PRCA.M392B5C2nkmtbh
WPS_3G2G_DRH_TRUNK_TIMEOUTACCUMULATIONINT8Total number of WPS call invocations for which trunk queuing for Directed Retry Handover has timed out.PRCA.M392B5C3nkmtbh
wps_attemptsACCUMULATIONINT8Requires trunks to point outside the MSC (counter 0.9).PRCA.M392B3C2nkmtbh
wps_calls_invokedACCUMULATIONINT8Total number of WPS calls invoked (counter 0.1). This counter is updated both in the VMSC and GMSC, and transit MSC.PRCA.M392B2C2nkmtbh
wps_channel_assignedACCUMULATIONINT8Total number of WPS call invocations for which radio traffic channel has been assigned (counter 0.2).PRCA.M392B2C3nkmtbh


MSC.Nokia.GSM.Rejected_Calls

This section describes the counters of M114

KPITypeData TypeDescriptionDerivationAdditional Summaries
rej_error_foundINTENSITYINTEGERTag appears at the end of the given counter group with field value 244 if an unexpected error situation has occurred.REJMSC.M114B2C13nkmtbh
rej_exchg_inc_percentx10INTENSITYFLOATThe ticket service rejection percentage (0.0...100.0) of all the signalling units of the exchange regardless of the computer units that have been under observation.REJMSC.M114B2C7nkmtbh
rej_exchg_incACCUMULATIONINT8The total sum of rejected incoming service requests (0...999999999) at the ticket service of all the signaling units of the exchange regardless of the computer units that have been under observation.REJMSC.M114B2C6nkmtbh
rej_exchg_outgoingACCUMULATIONINT8The number of rejected service requests (0...999999999) that have exceeded the higher rejection limit of the message buffer on the outgoing side. The number of rejected service requests that have exceeded the higher rejection limit of the CPU load on the incoming side.REJMSC.M114B2C8nkmtbh
rej_no_resp_from_lrmproINTENSITYINTEGERTag appears at the end of the given counter group with field value 242 if the signaling unit has not sent the required information for the following exchange-related counters: REJ_EXCHG_INC, REJ_EXCHG_INC_PERCENT*10, REJ_EXCHG_OUTGOING.REJMSC.M114B2C10nkmtbh
rej_no_resp_from_signprbINTENSITYINTEGERTag appears at the end of the given counter group with field value 243 if the required information has not been received from the signalling process family that provides counters of the measured object.REJMSC.M114B2C11nkmtbh
rej_observ_restartedINTENSITYINTEGERTag appears at the end of the given counter group with field value 16 if the signalling unit has not responded during the previous results accumulation period. Therefore, the observation has been restarted during the current results accumulation period. The counters is printed out during the following period.REJMSC.M114B2C12nkmtbh
rej_report_inquiry_failINTENSITYINTEGERTag appears at the end of the given counter group with field value 241 if only part of the required information is received from the signalling process family that provides the counters of the measured object.REJMSC.M114B2C9nkmtbh


MSC.Nokia.GSM.Routing

This section describes the field reporting of routing components measurement.

KPITypeData TypeDescriptionDerivationAdditional Summaries
rout_def_bund_rateeINTENSITYFLOATThe default highest possible passed call rate (per second) for a gapping gate (0...100).ROUTMSC.M137B2C2nkmtbh
rout_def_token_bankINTENSITYINTEGERDefault token bank size (1...32767).ROUTMSC.M137B2C1nkmtbh


MSC.Nokia.GSM.SCCP_Single_Meter

This table contains measurement data of one or more signalling networks.

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_hop_counterACCUMULATIONINT8Hop counter violationSINMSC.M219B2C16nkmtbh
rea_err_failACCUMULATIONINT8Reassembly error - Reassembly failedSINMSC.M219B2C13nkmtbh
rea_err_segmentACCUMULATIONINT8Reassembly error - Segment received out of sequenceSINMSC.M219B2C11nkmtbh
rea_err_spaceACCUMULATIONINT8Reassembly error - No reassembly spaceSINMSC.M219B2C12nkmtbh
rea_err_timer_expiryACCUMULATIONINT8Reassembly error - Timer T(reass) expirySINMSC.M219B2C10nkmtbh
sccp_from_localACCUMULATIONINT8Processed SCCP messages from a local subsystem.SINMSC.M219B2C2nkmtbh
sccp_to_localACCUMULATIONINT8Processed SCCP messages to a local subsystem.SINMSC.M219B2C1nkmtbh
sccp_totalACCUMULATIONINT8Processed SCCP messages, totalSINMSC.M219B2C5nkmtbh
sccp_userACCUMULATIONINT8Processed users independent SCCP messages.SINMSC.M219B2C4nkmtbh
seg_err_failACCUMULATIONINT8Segmentation error - Segmentation failedSINMSC.M219B2C15nkmtbh
seg_err_no_supportACCUMULATIONINT8Segmentation error - Segmenting not SupportedSINMSC.M219B2C14nkmtbh
stp_gtACCUMULATIONINT8STP messages requiring GT translation.SINMSC.M219B2C8nkmtbh
stpACCUMULATIONINT8Processed STP messagesSINMSC.M219B2C3nkmtbh
with_gt_from_localACCUMULATIONINT8Messages requiring GT translation from a local subsystem.SINMSC.M219B2C7nkmtbh
with_gt_to_localACCUMULATIONINT8Messages requiring GT translation to a local subsystem.SINMSC.M219B2C6nkmtbh
with_gt_totalACCUMULATIONINT8Messages requiring GT translation, totalSINMSC.M219B2C9nkmtbh


MSC.Nokia.GSM.SCCP_Subsystem_Local_Availability

This measurement contains measurement data of one or more signalling networks.N.B. There is a secondary key of signalling_network

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
dura_of_local_sccp_unavailableACCUMULATIONINT8Duration of the unavailability of a local SCCPLOCMSC.M218B2C5nkmtbh
duration_sccpACCUMULATIONINT8Duration of the unavailability of a local SCCPsubstr(LOCMSC.M218B2C5, 2, 0) * 86400 + substr(LOCMSC.M218B2C5, 2, 2) * 3600 + substr(LOCMSC.M218B2C5, 2, 4) * 60 + substr(LOCMSC.M218B2C5, 2,6 )nkmtbh
start_time_sccp_busyACCUMULATIONINT8Start of unavailability of a local SCCP due to maintenance busyLOCMSC.M218B2C2nkmtbh
start_time_sccp_congACCUMULATIONINT8Start of unavailability of a local SCCP due to congestionLOCMSC.M218B2C3nkmtbh
start_time_sccp_failACCUMULATIONINT8Start of unavailability of a local SCCP due to failureLOCMSC.M218B2C1nkmtbh
stop_time_sccpACCUMULATIONINT8Stop of unavailability of a local SCCPLOCMSC.M218B2C4nkmtbh


MSC.Nokia.GSM.SCCP_Subsystem

This measurement contains measurement data of one or more SCCP subsystems. N.B. There is a secondary key of signalling_network and also subsystem

The performance data measurements for this KPI group are recorded against the combination of MSC, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
csm_accepted_localACCUMULATIONINT8Acceptance of a coordinated state modification request by a local subsystemSUBMSC.M217B2C1nkmtbh
csm_accepted_remoteACCUMULATIONINT8Acceptance of a coordinated state modification request by a remote subsystemSUBMSC.M217B2C2nkmtbh
csm_rejected_localACCUMULATIONINT8Rejection of a coordinated state modification request by a local subsystemSUBMSC.M217B2C3nkmtbh
csm_rejected_remoteACCUMULATIONINT8Rejection of a coordinated state modification request by a remote subsystemSUBMSC.M217B2C4nkmtbh
dt1_receivedACCUMULATIONINT8DT 1 messages received from MTP per sink SSNSUBMSC.M217B2C15nkmtbh
dt1_transACCUMULATIONINT8DT 1 messages sent to MTP per source SSNSUBMSC.M217B2C16nkmtbh
dt2_receivedACCUMULATIONINT8DT 2 messages received from MTP per sink SSNSUBMSC.M217B2C17nkmtbh
dt2_transACCUMULATIONINT8DT 2 messages sent to MTP per source SSNSUBMSC.M217B2C18nkmtbh
ed_receivedACCUMULATIONINT8ED messages received from MTP per sink SSNSUBMSC.M217B2C19nkmtbh
ed_transACCUMULATIONINT8ED messages sent to MTP per source SSNSUBMSC.M217B2C20nkmtbh
err_segmentationACCUMULATIONINT8Messages too large for segmentationSUBMSC.M217B2C23nkmtbh
msg_all_localACCUMULATIONINT8All messages related to a local subsystemSUBMSC.M217B2C9nkmtbh
msg_from_local_with_gtACCUMULATIONINT8Messages addressed from a local subsystem that require GT translationSUBMSC.M217B2C8nkmtbh
msg_from_local_without_gtACCUMULATIONINT8Messages addressed from a local subsystem that do not require GT translationSUBMSC.M217B2C7nkmtbh
msg_received_class0ACCUMULATIONINT8All received messages in protocol class 0SUBMSC.M217B2C13nkmtbh
msg_received_class1ACCUMULATIONINT8All received messages in protocol class 1SUBMSC.M217B2C14nkmtbh
msg_redundantACCUMULATIONINT8All messages transmitted to the redundant subsystemSUBMSC.M217B2C10nkmtbh
msg_to_local_with_gtACCUMULATIONINT8Messages addressed to a local subsystem that require GT translationSUBMSC.M217B2C6nkmtbh
msg_to_local_withou_gtACCUMULATIONINT8Messages addressed to a local subsystem that do not require GT translationSUBMSC.M217B2C5nkmtbh
msg_trans_class0ACCUMULATIONINT8All transmitted messages in protocol class 0SUBMSC.M217B2C11nkmtbh
msg_trans_class1ACCUMULATIONINT8All transmitted messages in protocol class 1SUBMSC.M217B2C12nkmtbh
prohibited_start_timeACCUMULATIONINT8Start of local subsystem prohibitedSUBMSC.M217B2C21nkmtbh
prohibited_stop_timeACCUMULATIONINT8Stop of local subsystem prohibitedSUBMSC.M217B2C22nkmtbh


MSC.Nokia.GSM.Security_Report

This measurement contains the results of the security counter measurement. The measurement collects information about the system from the security point of view.N.B. There is a secondary key of security_counter

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
count_reset_timeINTENSITYINTEGERThe previous reset time of long term counters, for example, 1999051916000000SSEC.M176B0C2nkmtbh
critical_limitACCUMULATIONINT8Critical limit is not set for successful events. The operator cannot set a critical limit for this counter.SSEC.M176B17C2nkmtbh
lo_term_count_reset_ddINTENSITYINTEGERCounter gives the day of long term counters reset time.SSEC.M176B0C4nkmtbh
lo_term_count_reset_hourINTENSITYINTEGERCounter gives the hours of long term counters reset time.SSEC.M176B0C5nkmtbh
lo_term_count_reset_minINTENSITYINTEGERCounter gives the minutes of long term counters reset time.SSEC.M176B0C6nkmtbh
lo_term_count_reset_mmINTENSITYINTEGERCounter gives the month of long term counters reset time.SSEC.M176B0C3nkmtbh
lo_term_count_reset_secINTENSITYINTEGERCounter gives the seconds of long term counters reset time.SSEC.M176B0C7nkmtbh
long_term_totalACCUMULATIONINT8This counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B17C3nkmtbh
output_reasonACCUMULATIONINT8The reason for the report outputSSEC.M176B0C1nkmtbh
sec_critical_limit_10INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B10C2nkmtbh
sec_critical_limit_11INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B11C2nkmtbh
sec_critical_limit_12INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B12C2nkmtbh
sec_critical_limit_13INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B13C2nkmtbh
sec_critical_limit_14INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B14C2nkmtbh
sec_critical_limit_15INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B15C2nkmtbh
sec_critical_limit_16INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B16C2nkmtbh
sec_critical_limit_1INTENSITYFLOATCritical limit is not set for successful events. The operator cannot set a critical limit for this counter.SSEC.M176B1C2nkmtbh
sec_critical_limit_2INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B2C2nkmtbh
sec_critical_limit_3INTENSITYFLOATCritical limit is not set for successful events. The operator cannot set a critical limit for this counter.SSEC.M176B3C2nkmtbh
sec_critical_limit_4INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B4C2nkmtbh
sec_critical_limit_5INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B5C2nkmtbh
sec_critical_limit_6INTENSITYFLOATCritical limit is not set for successful events. The operator cannot set a critical limit for this counter.SSEC.M176B6C2nkmtbh
sec_critical_limit_7INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B7C2nkmtbh
sec_critical_limit_8INTENSITYFLOATCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.SSEC.M176B8C2nkmtbh
sec_critical_limit_9INTENSITYFLOATCritical limit is not set for creating new users. The operator cannot set a critical limit for this counter.SSEC.M176B9C2nkmtbh
sec_long_term_total_10ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B10C3nkmtbh
sec_long_term_total_11ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B11C3nkmtbh
sec_long_term_total_12ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B12C3nkmtbh
sec_long_term_total_13ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B13C3nkmtbh
sec_long_term_total_14ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B14C3nkmtbh
sec_long_term_total_15ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B15C3nkmtbh
sec_long_term_total_16ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B16C3nkmtbh
sec_long_term_total_1ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B1C3nkmtbh
sec_long_term_total_2ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B2C3nkmtbh
sec_long_term_total_3ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B3C3nkmtbh
sec_long_term_total_4ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B4C3nkmtbh
sec_long_term_total_5ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B5C3nkmtbh
sec_long_term_total_6ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B6C3nkmtbh
sec_long_term_total_7ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B7C3nkmtbh
sec_long_term_total_8ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B8C3nkmtbh
sec_long_term_total_9ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.SSEC.M176B9C3nkmtbh
sec_total_10ACCUMULATIONINT8Counter shows the total number of log writing failures during the reporting period.SSEC.M176B10C1nkmtbh
sec_total_11ACCUMULATIONINT8Counter shows the total number of command check errors during the reporting period.SSEC.M176B11C1nkmtbh
sec_total_12ACCUMULATIONINT8Counter shows the total number of authentication failures during the reporting period.SSEC.M176B12C1nkmtbh
sec_total_13ACCUMULATIONINT8Counter shows the total number of unknown IMSI numbers during the reporting period.SSEC.M176B13C1nkmtbh
sec_total_14ACCUMULATIONINT8Counter shows the total number of IMEI numbers found to be on the black list during the reporting period.SSEC.M176B14C1nkmtbh
sec_total_15ACCUMULATIONINT8Counter shows the total number of IMEI numbers found to be on the grey list during the reporting period.SSEC.M176B15C1nkmtbh
sec_total_16ACCUMULATIONINT8Counter shows the total number of unknown IMEI numbers during the reporting period.SSEC.M176B16C1nkmtbh
sec_total_1ACCUMULATIONINT8Counter shows the total number of successful events during the reporting period.SSEC.M176B1C1nkmtbh
sec_total_2ACCUMULATIONINT8Counter shows the total number of illegal login attempts during the reporting period.SSEC.M176B2C1nkmtbh
sec_total_3ACCUMULATIONINT8Counter shows the total number of successful events during the reporting period.SSEC.M176B3C1nkmtbh
sec_total_4ACCUMULATIONINT8Counter shows the total number of attempts to access a network element with an invalid username or password during the reporting period.SSEC.M176B4C1nkmtbh
sec_total_5ACCUMULATIONINT8Counter shows the total number of attempts to access a network element with inadequate access rights during the reporting period.SSEC.M176B5C1nkmtbh
sec_total_6ACCUMULATIONINT8Counter shows the total number of started MML sessions during the reporting period.SSEC.M176B6C1nkmtbh
sec_total_7ACCUMULATIONINT8Counter shows the total number of attempts to open an MML session with an invalid username or password during the reporting period.SSEC.M176B7C1nkmtbh
sec_total_8ACCUMULATIONINT8Counter shows the total number of attempts to give MML commands with inadequate access rights during the reporting period.SSEC.M176B8C1nkmtbh
sec_total_9ACCUMULATIONINT8Counter shows the total number of new usernames that have been created during the reporting period.SSEC.M176B9C1nkmtbh
totalACCUMULATIONINT8This counter shows the total number of successful events during the reporting period.SSEC.M176B17C1nkmtbh


MSC.Nokia.GSM.Setups

UPD setup data.

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
csts_upd_in_all_successACCUMULATIONINT8Number of all incoming successful setups in specified UPD during the report period.CSTSU.M386B4C3nkmtbh
csts_upd_in_aveACCUMULATIONINT8Average time of the durations of the successful incoming setups in UPD during the report period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSU.M386B4C7nkmtbh
csts_upd_in_long_successACCUMULATIONINT8Number of successful incoming setups when the time is over the defined setup time by PRFILE parameter.CSTSU.M386B4C4nkmtbh
csts_upd_in_max_successACCUMULATIONINT8Longest setup time in the UPD for the incoming direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSU.M386B4C6nkmtbh
csts_upd_in_min_successACCUMULATIONINT8The shortest setup time in the UPD for incoming direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSU.M386B4C5nkmtbh
csts_upd_out_all_successACCUMULATIONINT8Number of all outgoing successful setups in specified UPD during the report period.CSTSU.M386B4C8nkmtbh
csts_upd_out_aveACCUMULATIONINT8The average time of the durations of the outgoing successful setups in UPD during the report period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSU.M386B4C12nkmtbh
csts_upd_out_long_successACCUMULATIONINT8Number of outgoing successful setups when the time is over the defined setup time by PRFILE parameter.CSTSU.M386B4C9nkmtbh
csts_upd_out_max_successACCUMULATIONINT8The longest setup time in the UPD for the outgoing direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSU.M386B4C11nkmtbh
csts_upd_out_min_successACCUMULATIONINT8The shortest setup time in the UPD for the outgoing direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 millisecondsCSTSU.M386B4C10nkmtbh


MSC.Nokia.GSM.Signal_Clear_Code_Circuit_Group

KPI group not in use. This table contains information about the clear codes for circuit groups used in different phases of the call. N.B. There is a secondary key of msc_clear_code and also signal_protocol and also circuit_group_set

The performance data measurements for this KPI group are recorded against the combination of MSC, Circuit_Group_Set (circuit_group_set_id) , MSC_Clear_Code (msc_clear_code_id) and Signal_Protocol (signal_protocol_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_in_ringACCUMULATIONINT8(Obsolete in M13.5, CGRCC block now supported under ROUTE_IF object) The number of calls ending with clear code in ring phaseobsolete.obsoletenkmtbh
calls_in_signalACCUMULATIONINT8(Obsolete in M13.5, CGRCC block now supported under ROUTE_IF object) The number of calls ending with clear code in signalling phaseobsolete.obsoletenkmtbh
calls_in_speechACCUMULATIONINT8(Obsolete in M13.5, CGRCC block now supported under ROUTE_IF object) The number of calls ending with clear code in speech phaseobsolete.obsoletenkmtbh


MSC.Nokia.GSM.Signal_Clear_Code_Group

Signalling Clear Code by Group

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSCC_RINGACCUMULATIONINT8The number of clear codes in the ringing phaseCC1.M136B2C4nkmtbh
SSCC_SIGNALLINGACCUMULATIONINT8The number of clear codes in the signalling phaseCC1.M136B2C3nkmtbh
SSCC_SPEECHACCUMULATIONINT8The number of clear codes in the speech phaseCC1.M136B2C5nkmtbh


MSC.Nokia.GSM.Signal_Clear_Code

This table contains information about the individual clear codes for each signalling used in different phases of the call. N.B. There is a secondary key of msc_clear_code and also signal_protocol

The performance data measurements for this KPI group are recorded against the combination of MSC, MSC_Clear_Code (CC_ID) and Signal_Protocol (PROTOCOL_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_in_ringACCUMULATIONINT8The number of calls ending with clear code in ring phase.CC2.M135B2C3nkmtbh
calls_in_signalACCUMULATIONINT8The number of calls ending with clear code in signalling phaseCC2.M135B2C2nkmtbh
calls_in_speechACCUMULATIONINT8The number of calls ending with clear code in speech phaseCC2.M135B2C4nkmtbh


MSC.Nokia.GSM.Simultaneous_Calls

Simultaneous calls on the MSC by traffic type

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIMUL_DATA_PROV_RESTARTINTENSITYINT8Shows that if the statistics data provider program block is restarted in any of the signalling unit(s) during the period, the M396B3C1 counter is written (with value '1') under every record. Otherwise the counter is omitted.SIMCMSC.M396B3C1nkmtbh
SIMUL_MSC_AVG_SIM_CALLACCUMULATIONINT8Shows the average number of simultaneous calls (0...999999999).A sampling is done in each 30 seconds to determine the number of simultaneous calls in the MSC. The average is calculated by dividing the cumulative number of simultaneous calls by the number of samples.SIMCMSC.M396B2C2nkmtbh
SIMUL_MSC_PEAK_SIM_CALLINTENSITYINT8Provides the peak number of simultaneous calls during the measurement period (0...999999999).SIMCMSC.M396B2C3nkmtbh


MSC.Nokia.GSM.SIP_registration

Session Invitation Protocol data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
restart_in_stuACCUMULATIONINT8Indicates that duplex restart occurred in STU(s) during the measurement. The counters are unreliable. The field has an effect on all report parts. The possible value is 1, or this field does not appear in the report.SIPM.M357B1C3nkmtbh


MSC.Nokia.GSM.STU_Restart

STU Restarts

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIP_PROT_STU_RESTARTINTENSITYINT8This counter indicates that the STU has been restarted during the measured period and the presented counter values are not fully reliable.SIPPROT.M360B1C1nkmtbh
SIP_TCP_STU_RESTARTINTENSITYINT8Indicates that STU has been restarted during the measured period and the presented counter values are not fully reliable.SIPPROT.M360B11C1nkmtbh


MSC.Nokia.GSM.Subscriber_Facilities

This measurement contains the measurement results from the subscriber facilities usage times measurement, which is part of field reporting. N.B. There is a secondary key of subscriber_facility

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

KPITypeData TypeDescriptionDerivationAdditional Summaries
tot_usageACCUMULATIONINT8Total number of times the facility has been usedSERVI.M128B2C2nkmtbh
usage_activationsACCUMULATIONINT8The number of facility activations.SERVI.M128B2C3nkmtbh
usage_interrogationsACCUMULATIONINT8The number of facility interrogations.SERVI.M128B2C5nkmtbh
usage_passivationsACCUMULATIONINT8The number of facility passivations.SERVI.M128B2C4nkmtbh


MSC.Nokia.GSM.Subscribers_HLR

This section describes the key columns and counters of M339

KPITypeData TypeDescriptionDerivationAdditional Summaries
datamissing_in_subscvalues_hlrINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, that is, only a subset of the data could be collected. It means that the printed subscriber numbers per HLR are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)MSCVLR.M339B2C1nkmtbh
hsaverageINTENSITYFLOATAverage number of home subscribers belonging to the HLR displayed in the same line, during the reporting period. For the calculation of the average, the number of home subscribers is interrogated at fiveminute intervals. The maximum number of different HLR addresses in a report is 40.MSCVLR.M339B2C5nkmtbh


MSC.Nokia.GSM.TCAP_Messages

This table contains measurement data of one or more signalling links in the transaction capabilities application part.Related to messages

KPITypeData TypeDescriptionDerivationAdditional Summaries
msg_discardedACCUMULATIONINT8The number of messages discardedTCAPMSC.M220B5C2nkmtbh
received_abortACCUMULATIONINT8The number of received ABORT messagesTCAPMSC.M220B6C10nkmtbh
received_beginACCUMULATIONINT8The number of received BEGIN messagesTCAPMSC.M220B6C4nkmtbh
received_continueACCUMULATIONINT8The number of received CONTINUE messagesTCAPMSC.M220B6C6nkmtbh
received_endACCUMULATIONINT8The number of received END messagesTCAPMSC.M220B6C8nkmtbh
received_unidirectionalACCUMULATIONINT8The number of received UNIDIRECTIONAL messagesTCAPMSC.M220B6C2nkmtbh
tc_total_receivedACCUMULATIONINT8The number of received UNIDIRECTIONAL messagesTCAPMSC.M220B6C12nkmtbh
tc_total_transACCUMULATIONINT8The number of transmitted UNIDIRECTIONAL messagesTCAPMSC.M220B6C11nkmtbh
trans_abortACCUMULATIONINT8The number of transmitted ABORT messagesTCAPMSC.M220B6C9nkmtbh
trans_beginACCUMULATIONINT8The number of transmitted BEGIN messagesTCAPMSC.M220B6C3nkmtbh
trans_continueACCUMULATIONINT8The number of transmitted CONTINUE messagesTCAPMSC.M220B6C5nkmtbh
trans_endACCUMULATIONINT8The number of transmitted END messagesTCAPMSC.M220B6C7nkmtbh
trans_unidirectionalACCUMULATIONINT8The number of transmitted UNIDIRECTIONAL messagesTCAPMSC.M220B6C1nkmtbh


MSC.Nokia.GSM.TCAP_Performance

This table contains measurement data of one or more signalling links in the transaction capabilities application part.

KPITypeData TypeDescriptionDerivationAdditional Summaries
pa_receivedACCUMULATIONINT8The number of provider aborts receivedTCAPMSC.M220B5C3nkmtbh
received_tc_componentsACCUMULATIONINT8The number of received TC componentsTCAPMSC.M220B6C14nkmtbh
rej_receivedACCUMULATIONINT8The number of rejects receivedTCAPMSC.M220B5C4nkmtbh
tcl_cancelACCUMULATIONINT8The number of received TCL cancel indications for class 1 operationsTCAPMSC.M220B5C1nkmtbh
trans_tc_componentsACCUMULATIONINT8The number of transmitted TC componentsTCAPMSC.M220B6C13nkmtbh


MSC.Nokia.GSM.TCAP_Protocol_Error_In_Completion_Portion

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to protocol errors in the completion portion.

KPITypeData TypeDescriptionDerivationAdditional Summaries
comp_received_bad_structureACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: badly structured componentTCAPMSC.M220B3C5nkmtbh
comp_received_mistypedACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: mistyped componentTCAPMSC.M220B3C3nkmtbh
comp_received_ret_errorACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: return error unexpectedTCAPMSC.M220B3C15nkmtbh
comp_received_ret_resultACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: return result unexpectedTCAPMSC.M220B3C11nkmtbh
comp_received_unrecognizedACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: unrecognised componentTCAPMSC.M220B3C1nkmtbh
comp_trans_bad_structureACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: badly structured componentTCAPMSC.M220B3C6nkmtbh
comp_trans_mistypedACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: mistyped componentTCAPMSC.M220B3C4nkmtbh
comp_trans_ret_errorACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: return error unexpectedTCAPMSC.M220B3C16nkmtbh
comp_trans_unrecognizedACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: unrecognised componentTCAPMSC.M220B3C2nkmtbh
reject_rxed_unrec_invoke_id_reACCUMULATIONINT8Protocol error in comp. portion (reject rec.)-problem code: unrecognized invoke id. (RE)TCAPMSC.M220B3C13nkmtbh
reject_rxed_unrec_invoke_id_rrACCUMULATIONINT8Protocol error in comp. portion (reject rec.)- problem code: unrecognized invoke id. (RR)TCAPMSC.M220B3C9nkmtbh
reject_rxed_unrec_linked_idACCUMULATIONINT8Protocol error in comp. portion (reject rec.)- problem code: unrecognized linked id. TCAPMSC.M220B3C7nkmtbh
reject_sent_return_result_unexACCUMULATIONINT8Protocol error in comp. portion (reject sent)-problem code: return result unexpected TCAPMSC.M220B3C12nkmtbh
reject_sent_unrec_invoke_id_reACCUMULATIONINT8Protocol error in comp. portion (reject sent)- problem code: unrecognized invoke id. (RE)TCAPMSC.M220B3C14nkmtbh
reject_sent_unrec_invoke_id_rrACCUMULATIONINT8Protocol error in comp. portion (reject sent)-problem code: unrecognized invoke id. (RR)TCAPMSC.M220B3C10nkmtbh
reject_sent_unrec_linked_idACCUMULATIONINT8Protocol error in comp. portion (reject sent)- problem code: unrecognized linked idTCAPMSC.M220B3C8nkmtbh


MSC.Nokia.GSM.TCAP_Protocol_Error_In_Transaction_Portion

This table contains measurement data of one or more signalling links in the transaction capabilities application part.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ab_received_msg_typeACCUMULATIONINT8Protocol error in transaction portion (abort received) - unrecognised message typeTCAPMSC.M220B2C1nkmtbh
ab_received_rlimitACCUMULATIONINT8Protocol error in transaction portion (abort received) - resource limitationTCAPMSC.M220B2C9nkmtbh
ab_received_ta_bad_formatACCUMULATIONINT8Protocol error in transaction portion (abort received) - badly formatted transaction portionTCAPMSC.M220B2C5nkmtbh
ab_received_ta_incorrectACCUMULATIONINT8Protocol error in transaction portion (abort received) - incorrect transaction portionTCAPMSC.M220B2C3nkmtbh
ab_received_ta_unrecognizedACCUMULATIONINT8Protocol error in transaction portion (abort received) - unrecognized transaction identifierTCAPMSC.M220B2C7nkmtbh
ab_trans_msg_typeACCUMULATIONINT8Protocol error in transaction portion (abort sent) - unrecognised message typeTCAPMSC.M220B2C2nkmtbh
ab_trans_rlimitACCUMULATIONINT8Protocol error in transaction portion (abort sent) - resource limitationTCAPMSC.M220B2C10nkmtbh
ab_trans_ta_bad_formatACCUMULATIONINT8Protocol error in transaction portion (abort sent) - badly formatted transaction portionTCAPMSC.M220B2C6nkmtbh
ab_trans_ta_incorrectACCUMULATIONINT8Protocol error in transaction portion (abort sent) - incorrect transaction portionTCAPMSC.M220B2C4nkmtbh
ab_trans_ta_unrecognizedACCUMULATIONINT8Protocol error in transaction portion (abort sent) - unrecognised transaction identifierTCAPMSC.M220B2C8nkmtbh
err_transactionACCUMULATIONINT8The number of errors detected in the transaction portionTCAPMSC.M220B5C5nkmtbh


MSC.Nokia.GSM.TCAP_Transaction

This section describes the TC transactions meters measurement.N.B. There is a secondary key of signalling_network and also subsystem

The performance data measurements for this KPI group are recorded against the combination of MSC, Signalling_Network (SNET_ID) and Subsystem (SS_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
max_openINTENSITYINTEGERMaximum number of open transaction Ids during the periodTTRAMSC.M224B2C2nkmtbh
mean_durationINTENSITYINTEGERCumulative mean duration of transactionsTTRAMSC.M224B2C1nkmtbh
newACCUMULATIONINT8The number of new transactions during the periodTTRAMSC.M224B2C3nkmtbh
openINTENSITYINTEGERMean number of open transaction Ids during the periodTTRAMSC.M224B2C4nkmtbh


MSC.Nokia.GSM.TCAP_User_Generated_Problems

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to user generated problems

KPITypeData TypeDescriptionDerivationAdditional Summaries
reject_rxed_duplic_invoke_idACCUMULATIONINT8TC user generated problem (Reject received) - duplicate invoke id. ( 14.3a in ITU-T Q.752 )TCAPMSC.M220B4C1nkmtbh
reject_sent_duplic_invoke_idACCUMULATIONINT8TC user generated problem (Reject sent) -duplicate invoke id. ( 14.6a in ITU-T Q.752 )TCAPMSC.M220B4C2nkmtbh
tc_received_init_releaseACCUMULATIONINT8TC user generated problem (reject rec.) problem code: initiating releaseTCAPMSC.M220B4C9nkmtbh
tc_received_link_op_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unexpected link operationTCAPMSC.M220B4C13nkmtbh
tc_received_link_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: link response unexpectedTCAPMSC.M220B4C11nkmtbh
tc_received_mistyped_paramACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameterTCAPMSC.M220B4C5nkmtbh
tc_received_mistyped_reACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameter (RE)TCAPMSC.M220B4C21nkmtbh
tc_received_mistyped_rrACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameter (RR)TCAPMSC.M220B4C19nkmtbh
tc_received_rlimitACCUMULATIONINT8TC user generated problem (reject rec.) problem code: resource limitationTCAPMSC.M220B4C7nkmtbh
tc_received_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unexpected errorTCAPMSC.M220B4C17nkmtbh
tc_received_unknown_opACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unrecognised operationTCAPMSC.M220B4C3nkmtbh
tc_received_unrecognizedACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unrecognised errorTCAPMSC.M220B4C15nkmtbh
tc_trans_init_releaseACCUMULATIONINT8TC user generated problem (reject sent.) problem code: initiating releaseTCAPMSC.M220B4C10nkmtbh
tc_trans_link_op_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unexpected link operationTCAPMSC.M220B4C14nkmtbh
tc_trans_link_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: link response unexpectedTCAPMSC.M220B4C12nkmtbh
tc_trans_mistyped_paramACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameterTCAPMSC.M220B4C6nkmtbh
tc_trans_mistyped_reACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameter (RE)TCAPMSC.M220B4C22nkmtbh
tc_trans_mistyped_rrACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameter (RR)TCAPMSC.M220B4C20nkmtbh
tc_trans_rlimitACCUMULATIONINT8TC user generated problem (reject sent.) problem code: resource limitationTCAPMSC.M220B4C8nkmtbh
tc_trans_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unexpected errorTCAPMSC.M220B4C18nkmtbh
tc_trans_unknown_opACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unrecognised operationTCAPMSC.M220B4C4nkmtbh
tc_trans_unrecognizedACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unrecognised errorTCAPMSC.M220B4C16nkmtbh


MSC.Nokia.GSM.Traffic_Category_All_Types

This table contains the measurement results of the traffic category measurements.N.B.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ans_calls_tcACCUMULATIONINT8The number of answered calls. (OSS 3.1)TCGRP.M20B2C3nkmtbh
avr_traf_erlang_tcERLANGFLOATThe average traffic in Erlangs during the measurement period.TCGRP.M20B2C12nkmtbh
clear_code_group_1ACCUMULATIONINT8Calls registered in clear code group 1.TCGRP.M20B2C4nkmtbh
clear_code_group_2ACCUMULATIONINT8Calls registered in clear code group 2.TCGRP.M20B2C5nkmtbh
clear_code_group_3ACCUMULATIONINT8Calls registered in clear code group 3.TCGRP.M20B2C6nkmtbh
clear_code_group_4ACCUMULATIONINT8Calls registered in clear code group 4.TCGRP.M20B2C7nkmtbh
clear_code_group_5ACCUMULATIONINT8Calls registered in clear code group 5.TCGRP.M20B2C8nkmtbh
clear_code_group_6ACCUMULATIONINT8Calls registered in clear code group 6.TCGRP.M20B2C9nkmtbh
clear_code_group_7ACCUMULATIONINT8Calls registered in clear code group 7.TCGRP.M20B2C10nkmtbh
clear_code_group_8ACCUMULATIONINT8Calls registered in clear code group 8.TCGRP.M20B2C11nkmtbh
nbr_calls_tcACCUMULATIONINT8The number of calls made.TCGRP.M20B2C2nkmtbh
tcat_answ_trERLANGFLOATThe answered call duration, with possible values range from 0.0 to 999999.9 in erlangs.TCGRP.M20B2C17nkmtbh
tcat_data_prov_restartedACCUMULATIONINT8The tag appears at the end of the given counter group with field value 1 when the actual record is invalid.TCGRP.M20B2C14nkmtbh
tcat_intern_invalid_recINTENSITYINTEGERThis is to indicate whether the data in the actual record is valid or not. If the record data is valid, the counter would not appear in the report, otherwise it will be set to 1.TCGRP.M20B2C13nkmtbh
tcat_ring_amountACCUMULATIONINT8Number of calls that reached the ringing phase(0...9999999). Used only if Ring counter in traffic measurements feature is in use. When MSS receives the ACM message from the other MSS, Statistics saves that the call has reached the ringing phase.TCGRP.M20B2C15nkmtbh
tcat_succ_trERLANGFLOATThe successful call duration, with possible values range from 0.0 to 999999.9 in erlangs.TCGRP.M20B2C16nkmtbh
tcat_traffERLANGFLOATThe average traffic in Erlangs during the measurement period /100TCGRP.M20B2C12/100nkmtbh


MSC.Nokia.GSM.Traffic_Category

This table contains the measurement results of the traffic category measurements.N.B. There is a secondary key of 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
ans_calls_tcACCUMULATIONINT8The number of answered calls. (OSS 3.1)TC.M20B2C3nkmttbh
avr_traf_erlang_tcERLANGFLOATThe average traffic in Erlangs during the measurement period.TC.M20B2C12nkmttbh
clear_code_group_1ACCUMULATIONINT8Calls registered in clear code group 1.TC.M20B2C4nkmttbh
clear_code_group_2ACCUMULATIONINT8Calls registered in clear code group 2.TC.M20B2C5nkmttbh
clear_code_group_3ACCUMULATIONINT8Calls registered in clear code group 3.TC.M20B2C6nkmttbh
clear_code_group_4ACCUMULATIONINT8Calls registered in clear code group 4.TC.M20B2C7nkmttbh
clear_code_group_5ACCUMULATIONINT8Calls registered in clear code group 5.TC.M20B2C8nkmttbh
clear_code_group_6ACCUMULATIONINT8Calls registered in clear code group 6.TC.M20B2C9nkmttbh
clear_code_group_7ACCUMULATIONINT8Calls registered in clear code group 7.TC.M20B2C10nkmttbh
clear_code_group_8ACCUMULATIONINT8Calls registered in clear code group 8.TC.M20B2C11nkmttbh
nbr_calls_tcACCUMULATIONINT8The number of calls made.TC.M20B2C2nkmttbh
tcat_answ_trERLANGFLOATThe answered call duration, with possible values range from 0.0 to 999999.9 in erlangs.TC.M20B2C17nkmttbh
tcat_data_prov_restartedACCUMULATIONINT8The tag appears at the end of the given counter group with field value 1 when the actual record is invalid.TC.M20B2C14nkmttbh
tcat_intern_invalid_recINTENSITYINTEGERThis is to indicate whether the data in the actual record is valid or not. If the record data is valid, the counter would not appear in the report, otherwise it will be set to 1.TC.M20B2C13nkmttbh
tcat_ring_amountACCUMULATIONINT8Number of calls that reached the ringing phase(0...9999999). Used only if Ring counter in traffic measurements feature is in use. When MSS receives the ACM message from the other MSS, Statistics saves that the call has reached the ringing phase.TC.M20B2C15nkmttbh
tcat_succ_trERLANGFLOATThe successful call duration, with possible values range from 0.0 to 999999.9 in erlangs.TC.M20B2C16nkmttbh
tcat_traffERLANGFLOATThe average traffic in Erlangs during the measurement period /100TC.M20B2C12/100nkmttbh


MSC.Nokia.GSM.Trafficability

This measurement contains the measurement results from the trafficability performance measurement, which is part of field reporting.

KPITypeData TypeDescriptionDerivationAdditional Summaries
answeredACCUMULATIONINT8The number of answered calls.MSCTRAF.M130B2C3nkmtbh
calls_ccgrp_1ACCUMULATIONINT8The number of calls ended in clear code group 1.MSCTRAF.M130B2C7nkmtbh
calls_ccgrp_2ACCUMULATIONINT8The number of calls ended in clear code group 2.MSCTRAF.M130B2C9nkmtbh
calls_ccgrp_3ACCUMULATIONINT8The number of calls ended in clear code group 3.MSCTRAF.M130B2C11nkmtbh
calls_ccgrp_4ACCUMULATIONINT8The number of calls ended in clear code group 4.MSCTRAF.M130B2C13nkmtbh
calls_ccgrp_5ACCUMULATIONINT8The number of calls ended in clear code group 5.MSCTRAF.M130B2C15nkmtbh
calls_ccgrp_6ACCUMULATIONINT8The number of calls ended in clear code group 6.MSCTRAF.M130B2C17nkmtbh
calls_ccgrp_7ACCUMULATIONINT8The number of calls ended in clear code group 7.MSCTRAF.M130B2C19nkmtbh
calls_ccgrp_8ACCUMULATIONINT8The number of calls ended in clear code group 8.MSCTRAF.M130B2C21nkmtbh
not_answeredACCUMULATIONINT8The number of unanswered calls.MSCTRAF.M130B2C5nkmtbh
ratio_answeredINTENSITYFLOATThe ratio of answered calls.MSCTRAF.M130B2C4nkmtbh
ratio_calls_ccgrp_1INTENSITYFLOATThe ratio of calls ended in clear code group 1.MSCTRAF.M130B2C8nkmtbh
ratio_calls_ccgrp_2INTENSITYFLOATThe ratio of calls ended in clear code group 2.MSCTRAF.M130B2C10nkmtbh
ratio_calls_ccgrp_3INTENSITYFLOATThe ratio of calls ended in clear code group 3.MSCTRAF.M130B2C12nkmtbh
ratio_calls_ccgrp_4INTENSITYFLOATThe ratio of calls ended in clear code group 4.MSCTRAF.M130B2C14nkmtbh
ratio_calls_ccgrp_5INTENSITYFLOATThe ratio of calls ended in clear code group 5.MSCTRAF.M130B2C16nkmtbh
ratio_calls_ccgrp_6INTENSITYFLOATThe ratio of calls ended in clear code group 6.MSCTRAF.M130B2C18nkmtbh
ratio_calls_ccgrp_7INTENSITYFLOATThe ratio of calls ended in clear code group 7.MSCTRAF.M130B2C20nkmtbh
ratio_calls_ccgrp_8INTENSITYFLOATThe ratio of calls ended in clear code group 8.MSCTRAF.M130B2C22nkmtbh
ratio_not_answeredINTENSITYFLOATThe ratio of unanswered calls.MSCTRAF.M130B2C6nkmtbh
tot_callsACCUMULATIONINT8The total number of incoming calls (bids).MSCTRAF.M130B2C1nkmtbh
trp_no_of_bids_x100INTENSITYFLOATThe number of answered calls in per cents. If the percentage contains 4 digits then the last 2 digits express the decimal value. If the percentage contains 3 digits then the last digit expresses the decimal value.MSCTRAF.M130B2C2nkmtbh


MSC.Nokia.GSM.TRFO

Transcoder free operation data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
CODEC_MODIFICATION_ATTEMPTACCUMULATIONINT8Shows the number of attempted codec modification procedures.The counter is updated when MSC Server sends the APM message and where the actionindicator is set to "modify codec".TRFO.M388B2C12nkmtbh
CODEC_NEGOTIATION_ATTEMPTACCUMULATIONINT8Shows the number of codec negotiation attempt procedures. The counter is updated when Codec List IE is sent in the IAM message.TRFO.M388B2C10nkmtbh
SUCC_CODEC_MODIFICATIONACCUMULATIONINT8Shows the number of successful codec modification procedures.The counter is updated when the MSC Server receives the APM message and theaction indicator is set to "successful codec modification".TRFO.M388B2C13nkmtbh
SUCC_CODEC_NEGOTIATIONACCUMULATIONINT8Shows the number of successful codec negotiation procedure. Thecounter is updated if APM message is received and the action indicator fieldis set to "selected codec" and the message contains the selected codec.TRFO.M388B2C11nkmtbh
TRFO_ALL_TIME_WBAMRACCUMULATIONINT8Counter which is updated if the call was full time TRFO and the WB-AMR codec was used.TRFO.M388B2C14nkmtbh
trfo_all_timeACCUMULATIONINT8Total number of calls in the MSS that do not use transcoder resources during the whole call.TRFO.M388B2C2nkmtbh
trfo_candidate_failedACCUMULATIONINT8Number of calls in the MSS that may not use transcoder resources by the nature of the call, but for some reason transcoding is needed.TRFO.M388B2C3nkmtbh
trfo_data_prov_restartedACCUMULATIONINT8If the data provider in the signalling unit or some signalling units have been restarted during the reporting period, the report data might not be reliable. In this case, the DATA PROVIDER RESTARTED DURING THE PERIOD text appears at the end of the ASCII rTRFO.M388B2C9nkmtbh
trfo_internal_all_timeACCUMULATIONINT8Total number of calls originating and terminating in the MSS that do not use transcoder resources during the whole call.TRFO.M388B2C6nkmtbh
trfo_internal_candidate_failedACCUMULATIONINT8Total number of calls originating and terminating in the MSS that may not use transcoder resources by the nature of the call, but for some reason transcoding is needed.TRFO.M388B2C7nkmtbh
trfo_internal_non_candidateACCUMULATIONINT8Total number of calls originating and terminating in the MSS that use transcoder resources by the nature of the call.TRFO.M388B2C8nkmtbh
trfo_internal_part_timeACCUMULATIONINT8Total number of calls originating and terminating in the MSS that do not use transcoder resources for some time during the call.TRFO.M388B2C5nkmtbh
trfo_non_candidateACCUMULATIONINT8Total number of calls in the MSS that use transcoder resources by the nature of the call.TRFO.M388B2C4nkmtbh
trfo_part_timeACCUMULATIONINT8Total number of calls in the MSS that do not use transcoder resources for some time during the call.TRFO.M388B2C1nkmtbh


MSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN

Unlicenced mobile access inter PLMN data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_in_inter_p_gsm_to_uma_failPERCENTAGEFLOATPercentage unsuccessful incoming inter- PLMN GSM-UMA handovers.percentfail({in_inter_p_gsm_to_uma_fail}, ({in_inter_p_gsm_to_uma_succ} + {in_inter_p_gsm_to_uma_fail}))nkmtbh
%_in_inter_p_gsm_to_uma_succPERCENTAGEFLOATPercentage successful incoming inter- PLMN GSM-UMA handovers.percentok({in_inter_p_gsm_to_uma_succ}, ({in_inter_p_gsm_to_uma_succ} + {in_inter_p_gsm_to_uma_fail}))nkmtbh
%_in_inter_p_uma_to_gsm_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-PLMN UMA-GSM handovers.percentfail({in_inter_p_uma_to_gsm_fail}, ({in_inter_p_uma_to_gsm_succ} + {in_inter_p_uma_to_gsm_fail}))nkmtbh
%_in_inter_p_uma_to_gsm_succPERCENTAGEFLOATPercentage successful incoming inter-PLMN UMA-GSM handovers.percentok({in_inter_p_uma_to_gsm_succ}, ({in_inter_p_uma_to_gsm_succ} + {in_inter_p_uma_to_gsm_fail}))nkmtbh
%_in_inter_p_uma_to_umts_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-PLMN UMA-UMTS handovers.percentfail({in_inter_p_uma_to_umts_fail}, ({in_inter_p_uma_to_umts_succ} + {in_inter_p_uma_to_umts_fail}))nkmtbh
%_in_inter_p_uma_to_umts_succPERCENTAGEFLOATPercentage successful incoming inter-PLMN UMA-UMTS handovers.percentok({in_inter_p_uma_to_umts_succ}, ({in_inter_p_uma_to_umts_succ} + {in_inter_p_uma_to_umts_fail}))nkmtbh
%_in_inter_p_umts_to_uma_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-PLMN UMTS-UMA handovers.percentfail({in_inter_p_umts_to_uma_fail}, ({in_inter_p_umts_to_uma_succ} + {in_inter_p_umts_to_uma_fail}))nkmtbh
%_in_inter_p_umts_to_uma_succPERCENTAGEFLOATPercentage successful incoming inter-PLMN UMTS-UMA handovers.percentok({in_inter_p_umts_to_uma_succ}, ({in_inter_p_umts_to_uma_succ} + {in_inter_p_umts_to_uma_fail}))nkmtbh
dropped_callsACCUMULATIONINT8Number of calls dropped{in_inter_p_gsm_to_uma_drop} + {in_inter_p_umts_to_uma_drop} + {in_inter_p_uma_to_gsm_drop} + {in_inter_p_uma_to_umts_drop}nkmtbh
in_inter_p_gsm_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN GSM-UMA handovers.HO1.M81B3C175nkmtbh
in_inter_p_gsm_to_uma_failACCUMULATIONINT8Number of unsuccessful incoming inter- PLMN GSM-UMA handovers.HO1.M81B3C174nkmtbh
in_inter_p_gsm_to_uma_succACCUMULATIONINT8Number of successful incoming inter- PLMN GSM-UMA handovers.HO1.M81B3C173nkmtbh
in_inter_p_uma_to_gsm_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN UMA-GSM handovers.HO1.M81B3C181nkmtbh
in_inter_p_uma_to_gsm_failACCUMULATIONINT8Number of unsuccessful incoming inter- PLMN UMA-GSM handovers.HO1.M81B3C180nkmtbh
in_inter_p_uma_to_gsm_succACCUMULATIONINT8Number of successful incoming inter- PLMN UMA-GSM handovers.HO1.M81B3C179nkmtbh
in_inter_p_uma_to_umts_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN UMA-UMTS handovers.HO1.M81B3C184nkmtbh
in_inter_p_uma_to_umts_failACCUMULATIONINT8Number of unsuccessful incoming inter- PLMN UMA-UMTS handovers.HO1.M81B3C183nkmtbh
in_inter_p_uma_to_umts_succACCUMULATIONINT8Number of successful incoming inter- PLMN UMA-UMTS handovers.HO1.M81B3C182nkmtbh
in_inter_p_umts_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN UMTS-UMA handovers.HO1.M81B3C178nkmtbh
in_inter_p_umts_to_uma_failACCUMULATIONINT8Number of unsuccessful incoming inter- PLMN UMTS-UMA handovers.HO1.M81B3C177nkmtbh
in_inter_p_umts_to_uma_succACCUMULATIONINT8Number of successful incoming inter- PLMN UMTS-UMA handovers.HO1.M81B3C176nkmtbh


MSC.Nokia.GSM.UMA_handovers_inter_MSC

Unlicenced mobile access inter MSC data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_in_inter_msc_gsm_to_uma_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC GSM-UMA handovers.percentfail({in_inter_msc_gsm_to_uma_fail}, ({in_inter_msc_gsm_to_uma_succ} + {in_inter_msc_gsm_to_uma_fail}))nkmtbh
%_in_inter_msc_gsm_to_uma_succPERCENTAGEFLOATPercentage successful incoming inter-MSC GSM-UMA handovers.percentok({in_inter_msc_gsm_to_uma_succ}, ({in_inter_msc_gsm_to_uma_succ} + {in_inter_msc_gsm_to_uma_fail}))nkmtbh
%_in_inter_msc_uma_to_gsm_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC UMA-GSM handovers.percentfail({in_inter_msc_uma_to_gsm_fail}, ({in_inter_msc_uma_to_gsm_succ} + {in_inter_msc_uma_to_gsm_fail}))nkmtbh
%_in_inter_msc_uma_to_gsm_succPERCENTAGEFLOATPercentage successful incoming inter-MSC UMA-GSM handovers.percentok({in_inter_msc_uma_to_gsm_succ}, ({in_inter_msc_uma_to_gsm_succ} + {in_inter_msc_uma_to_gsm_fail}))nkmtbh
%_in_inter_msc_uma_to_umts_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC UMA-UMTS handovers.percentfail({in_inter_msc_uma_to_umts_fail}, ({in_inter_msc_uma_to_umts_succ} + {in_inter_msc_uma_to_umts_fail}))nkmtbh
%_in_inter_msc_uma_to_umts_succPERCENTAGEFLOATPercentage successful incoming inter-MSC UMA-UMTS handovers.percentok({in_inter_msc_uma_to_umts_succ}, ({in_inter_msc_uma_to_umts_succ} + {in_inter_msc_uma_to_umts_fail}))nkmtbh
%_in_inter_msc_umts_to_uma_failPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC UMTS-UMA handovers.percentfail({in_inter_msc_umts_to_uma_fail}, ({in_inter_msc_umts_to_uma_succ} + {in_inter_msc_umts_to_uma_fail}))nkmtbh
%_in_inter_msc_umts_to_uma_succPERCENTAGEFLOATPercentage successful incoming inter-MSC UMTS-UMA handovers.percentok({in_inter_msc_umts_to_uma_succ}, ({in_inter_msc_umts_to_uma_succ} + {in_inter_msc_umts_to_uma_fail}))nkmtbh
%_out_inter_msc_gsm_to_uma_failPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC GSM-UMA handovers.percentfail({out_inter_msc_gsm_to_uma_fail}, ({out_inter_msc_gsm_to_uma_succ} + {out_inter_msc_gsm_to_uma_fail}))nkmtbh
%_out_inter_msc_gsm_to_uma_succPERCENTAGEFLOATPercentage successful outgoing inter-MSC GSM-UMA handovers.percentok({out_inter_msc_gsm_to_uma_succ}, ({out_inter_msc_gsm_to_uma_succ} + {out_inter_msc_gsm_to_uma_fail}))nkmtbh
%_out_inter_msc_uma_to_gsm_failPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC UMA-GSM handovers.percentfail({out_inter_msc_uma_to_gsm_fail}, ({out_inter_msc_uma_to_gsm_succ} + {out_inter_msc_uma_to_gsm_fail}))nkmtbh
%_out_inter_msc_uma_to_gsm_succPERCENTAGEFLOATPercentage successful outgoing inter-MSC UMA-GSM handovers.percentok({out_inter_msc_uma_to_gsm_succ}, ({out_inter_msc_uma_to_gsm_succ} + {out_inter_msc_uma_to_gsm_fail}))nkmtbh
%_out_inter_msc_uma_to_umts_failPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC UMA-UMTS handovers.percentfail({out_inter_msc_uma_to_umts_fail}, ({out_inter_msc_uma_to_umts_succ} + {out_inter_msc_uma_to_umts_fail}))nkmtbh
%_out_inter_msc_uma_to_umts_succPERCENTAGEFLOATPercentage successful outgoing inter-MSC UMA-UMTS handovers.percentok({out_inter_msc_uma_to_umts_succ}, ({out_inter_msc_uma_to_umts_succ} + {out_inter_msc_uma_to_umts_fail}))nkmtbh
%_out_inter_msc_umts_to_uma_failPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC UMTS-UMA handovers.percentfail({out_inter_msc_umts_to_uma_fail}, ({out_inter_msc_umts_to_uma_succ}+ {out_inter_msc_umts_to_uma_fail}))nkmtbh
%_out_inter_msc_umts_to_uma_succPERCENTAGEFLOATPercentage successful outgoing inter-MSC UMTS-UMA handovers.percentok({out_inter_msc_umts_to_uma_succ}, ({out_inter_msc_umts_to_uma_succ}+ {out_inter_msc_umts_to_uma_fail}))nkmtbh
dropped_callsACCUMULATIONINT8Dropped calls.{in_inter_msc_gsm_to_uma_drop} + {in_inter_msc_umts_to_uma_drop} + {in_inter_msc_uma_to_gsm_drop} + {in_inter_msc_uma_to_umts_drop} + {out_inter_msc_gsm_to_uma_drop} + {out_inter_msc_umts_to_uma_drop} + {out_inter_msc_uma_to_gsm_drop} + {out_inter_msc_uma_to_umts_drop}nkmtbh
in_inter_msc_gsm_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-MSC GSM-UMA handovers.HO1.M81B3C147nkmtbh
in_inter_msc_gsm_to_uma_failACCUMULATIONINT8Number of unsuccessful incoming inter- MSC GSM-UMA handovers.HO1.M81B3C146nkmtbh
in_inter_msc_gsm_to_uma_succACCUMULATIONINT8Number of successful incoming inter- MSC GSM-UMA handovers.HO1.M81B3C145nkmtbh
in_inter_msc_uma_to_gsm_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-MSC UMA-GSM handovers.HO1.M81B3C153nkmtbh
in_inter_msc_uma_to_gsm_failACCUMULATIONINT8Number of unsuccessful incoming inter- MSC UMA-GSM handovers.HO1.M81B3C152nkmtbh
in_inter_msc_uma_to_gsm_succACCUMULATIONINT8Number of successful incoming inter- MSC UMA-GSM handovers.HO1.M81B3C151nkmtbh
in_inter_msc_uma_to_umts_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-MSC UMA-UMTS handovers.HO1.M81B3C156nkmtbh
in_inter_msc_uma_to_umts_failACCUMULATIONINT8Number of unsuccessful incoming inter- MSC UMA-UMTS handovers.HO1.M81B3C155nkmtbh
in_inter_msc_uma_to_umts_succACCUMULATIONINT8Number of successful incoming inter- MSC UMA-UMTS handovers.HO1.M81B3C154nkmtbh
in_inter_msc_umts_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed incoming inter-MSC UMTS-UMAHO1.M81B3C150nkmtbh
in_inter_msc_umts_to_uma_failACCUMULATIONINT8Number of unsuccessful incoming inter- MSC UMTS-UMA handovers.HO1.M81B3C149nkmtbh
in_inter_msc_umts_to_uma_succACCUMULATIONINT8Number of successful incoming inter- MSC UMTS-UMA handovers.HO1.M81B3C148nkmtbh
out_inter_msc_gsm_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC GSM-UMA handoversHO1.M81B3C160nkmtbh
out_inter_msc_gsm_to_uma_failACCUMULATIONINT8Number of unsuccessful outgoing inter- MSC GSM-UMA handovers.HO1.M81B3C158nkmtbh
out_inter_msc_gsm_to_uma_reestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC GSM-UMA handovers.HO1.M81B3C159nkmtbh
out_inter_msc_gsm_to_uma_succACCUMULATIONINT8Number of successful outgoing inter-MSC GSM-UMA handovers.HO1.M81B3C157nkmtbh
out_inter_msc_uma_to_gsm_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC UMA-GSM handovers.HO1.M81B3C168nkmtbh
out_inter_msc_uma_to_gsm_failACCUMULATIONINT8Number of unsuccessful outgoing inter- MSC UMA-GSM handovers.HO1.M81B3C166nkmtbh
out_inter_msc_uma_to_gsm_reestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC UMA-GSM handovers.HO1.M81B3C167nkmtbh
out_inter_msc_uma_to_gsm_succACCUMULATIONINT8Number of successful outgoing inter-MSC UMA-GSM handovers.HO1.M81B3C165nkmtbh
out_inter_msc_uma_to_umts_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC UMA-UMTS handovers.HO1.M81B3C172nkmtbh
out_inter_msc_uma_to_umts_failACCUMULATIONINT8Number of unsuccessful outgoing inter- MSC UMA-UMTS handoversHO1.M81B3C170nkmtbh
out_inter_msc_uma_to_umts_rstACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC UMA-UMTS handoversHO1.M81B3C171nkmtbh
out_inter_msc_uma_to_umts_succACCUMULATIONINT8Number of successful outgoing inter-MSC UMA-UMTS handovers.HO1.M81B3C169nkmtbh
out_inter_msc_umts_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC UMTS-UMA handoversHO1.M81B3C164nkmtbh
out_inter_msc_umts_to_uma_failACCUMULATIONINT8Number of unsuccessful outgoing inter- MSC UMTS-UMA handovers.HO1.M81B3C162nkmtbh
out_inter_msc_umts_to_uma_rstACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC UMTS-UMA handovers.HO1.M81B3C163nkmtbh
out_inter_msc_umts_to_uma_succACCUMULATIONINT8Number of successful outgoing inter-MSC UMTS-UMA handovers.HO1.M81B3C161nkmtbh


MSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC

Unlicenced mobile access inter-PLMN intra-MSC data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_intrp_intramsc_gsm_to_uma_failPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC GSM-UMA handoverspercentfail({intrp_intramsc_gsm_to_uma_fail}, ({intrp_intramsc_gsm_to_uma_succ} + {intrp_intramsc_gsm_to_uma_fail}))nkmtbh
%_intrp_intramsc_gsm_to_uma_succPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC GSM-UMA handoverspercentok({intrp_intramsc_gsm_to_uma_succ}, ({intrp_intramsc_gsm_to_uma_succ} + {intrp_intramsc_gsm_to_uma_fail}))nkmtbh
%_intrp_intramsc_uma_to_gsm_failPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC UMA-GSM handovers.percentfail({intrp_intramsc_uma_to_gsm_fail}, ({intrp_intramsc_uma_to_gsm_succ} + {intrp_intramsc_uma_to_gsm_fail}))nkmtbh
%_intrp_intramsc_uma_to_gsm_succPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC UMA-GSM handovers.percentok({intrp_intramsc_uma_to_gsm_succ}, ({intrp_intramsc_uma_to_gsm_succ} + {intrp_intramsc_uma_to_gsm_fail}))nkmtbh
%_intrp_intramsc_uma_to_umts_faiPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC UMA-UMTS handovers.percentfail({intrp_intramsc_uma_to_umts_fai}, ({intrp_intramsc_uma_to_umts_suc} + {intrp_intramsc_uma_to_umts_fai}))nkmtbh
%_intrp_intramsc_uma_to_umts_sucPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC UMA-UMTS handovers.percentok({intrp_intramsc_uma_to_umts_suc}, ({intrp_intramsc_uma_to_umts_suc} + {intrp_intramsc_uma_to_umts_fai}))nkmtbh
%_intrp_intramsc_umts_to_uma_faiPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC UMTS-UMA handovers.percentfail({intrp_intramsc_umts_to_uma_fai}, ({intrp_intramsc_umts_to_uma_suc} + {intrp_intramsc_umts_to_uma_fai}))nkmtbh
%_intrp_intramsc_umts_to_uma_sucPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC UMTS-UMA handovers.percentok({intrp_intramsc_umts_to_uma_suc}, ({intrp_intramsc_umts_to_uma_suc} + {intrp_intramsc_umts_to_uma_fai}))nkmtbh
dropped_callsACCUMULATIONINT8Dropped calls.{intrp_intramsc_gsm_to_uma_drop} + {intrp_intramsc_umts_to_uma_drp} + {intrp_intramsc_uma_to_gsm_drop} + {intrp_intramsc_uma_to_umts_drp}nkmtbh
intrp_intramsc_gsm_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC GSM-UMAHO1.M81B3C132nkmtbh
intrp_intramsc_gsm_to_uma_failACCUMULATIONINT8Number of unsuccessful inter-PLMN intra-MSC GSM-UMA handovers.HO1.M81B3C130nkmtbh
intrp_intramsc_gsm_to_uma_rstACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra-MSC GSMUMA handovers.HO1.M81B3C131nkmtbh
intrp_intramsc_gsm_to_uma_succACCUMULATIONINT8Number of successful inter-PLMN intra-MSC GSM-UMA handoversHO1.M81B3C129nkmtbh
intrp_intramsc_uma_to_gsm_dropACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC UMA-GSM handovers.HO1.M81B3C140nkmtbh
intrp_intramsc_uma_to_gsm_failACCUMULATIONINT8Number of unsuccessful inter-PLMN intra-MSC UMA-GSM handovers.HO1.M81B3C138nkmtbh
intrp_intramsc_uma_to_gsm_rstACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra-MSC UMAGSM handovers.HO1.M81B3C139nkmtbh
intrp_intramsc_uma_to_gsm_succACCUMULATIONINT8Number of successful inter-PLMN intra-MSC UMA-GSM handovers.HO1.M81B3C137nkmtbh
intrp_intramsc_uma_to_umts_drpACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC UMA-UMTS handovers.HO1.M81B3C144nkmtbh
intrp_intramsc_uma_to_umts_faiACCUMULATIONINT8Number of unsuccessful inter-PLMN intra-MSC UMA-UMTS handovers.HO1.M81B3C142nkmtbh
intrp_intramsc_uma_to_umts_rstACCUMULATIONINT8Number of successful re-establishmentsin failed inter-PLMN intra-MSC UMAUMTS handovers.HO1.M81B3C143nkmtbh
intrp_intramsc_uma_to_umts_sucACCUMULATIONINT8Number of successful inter-PLMN intra-MSC UMA-UMTS handovers.HO1.M81B3C141nkmtbh
intrp_intramsc_umts_to_uma_drpACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC UMTS-UMA handovers.HO1.M81B3C136nkmtbh
intrp_intramsc_umts_to_uma_faiACCUMULATIONINT8Number of unsuccessful inter-PLMN intra-MSC UMTS-UMA handovers.HO1.M81B3C134nkmtbh
intrp_intramsc_umts_to_uma_rstACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra-MSC UMTSUMA handovers.HO1.M81B3C135nkmtbh
intrp_intramsc_umts_to_uma_sucACCUMULATIONINT8Number of successful inter-PLMN intra-MSC UMTS-UMA handovers.HO1.M81B3C133nkmtbh


MSC.Nokia.GSM.UMA_handovers_intra_MSC

Unlicenced mobile access Intra MSC data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_intra_msc_gsm_to_uma_failPERCENTAGEFLOATPercentage unsuccessful intra-MSC GSM UMA handovers.percentfail({intra_msc_gsm_to_uma_fail}, ({intra_msc_gsm_to_uma_succ} + {intra_msc_gsm_to_uma_fail}))nkmtbh
%_intra_msc_gsm_to_uma_succPERCENTAGEFLOATPercentage successful intra-MSC GSM UMA handovers.percentok({intra_msc_gsm_to_uma_succ}, ({intra_msc_gsm_to_uma_succ} + {intra_msc_gsm_to_uma_fail}))nkmtbh
%_intra_msc_uma_to_gsm_failPERCENTAGEFLOATPercentage unsuccessful intra-MSC UMA GSM handovers.percentfail({intra_msc_uma_to_gsm_fail}, ({intra_msc_uma_to_gsm_succ} + {intra_msc_uma_to_gsm_fail}))nkmtbh
%_intra_msc_uma_to_gsm_succPERCENTAGEFLOATPercentage successful intra-MSC UMA GSM handovers.percentok({intra_msc_uma_to_gsm_succ}, ({intra_msc_uma_to_gsm_succ} + {intra_msc_uma_to_gsm_fail}))nkmtbh
%_intra_msc_uma_to_umts_failPERCENTAGEFLOATPercentage unsuccessfull intra-MSC UMA UMTS handovers.percentfail({intra_msc_uma_to_umts_fail}, ({intra_msc_uma_to_umts_succ} + {intra_msc_uma_to_umts_fail}))nkmtbh
%_intra_msc_uma_to_umts_succPERCENTAGEFLOATPercentage successfull intra-MSC UMA UMTS handovers.percentok({intra_msc_uma_to_umts_succ}, ({intra_msc_uma_to_umts_succ} + {intra_msc_uma_to_umts_fail}))nkmtbh
%_intra_msc_umts_to_uma_failPERCENTAGEFLOATPercentage unsuccessfull intra-MSC UMTS UMA handovers.percentfail({intra_msc_umts_to_uma_fail}, ({intra_msc_umts_to_uma_succ} + {intra_msc_umts_to_uma_fail}))nkmtbh
%_intra_msc_umts_to_uma_succPERCENTAGEFLOATPercentage successfull intra-MSC UMTS UMA handovers.percentok({intra_msc_umts_to_uma_succ}, ({intra_msc_umts_to_uma_succ} + {intra_msc_umts_to_uma_fail}))nkmtbh
dropped_callsACCUMULATIONINT8Dropped calls.{intra_msc_gsm_to_uma_drop} + {intra_msc_umts_to_uma_drop} + {intra_msc_uma_to_gsm_drop} + {intra_msc_uma_to_umts_drop}nkmtbh
intra_msc_gsm_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed intra-MSC GSM-UMA handoversHO1.M81B3C116nkmtbh
intra_msc_gsm_to_uma_failACCUMULATIONINT8Number of unsuccessful intra-MSC GSM UMA handovers.HO1.M81B3C114nkmtbh
intra_msc_gsm_to_uma_reestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC GSM-UMA handovers.HO1.M81B3C115nkmtbh
intra_msc_gsm_to_uma_succACCUMULATIONINT8Number of successful intra-MSC GSM UMA handovers.HO1.M81B3C113nkmtbh
intra_msc_uma_to_gsm_dropACCUMULATIONINT8Number of calls dropped due to failed intra-MSC UMA-GSM handovers.HO1.M81B3C124nkmtbh
intra_msc_uma_to_gsm_failACCUMULATIONINT8Number of unsuccessful intra-MSC UMA GSM handovers.HO1.M81B3C122nkmtbh
intra_msc_uma_to_gsm_reestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC UMA-GSM handovers.HO1.M81B3C123nkmtbh
intra_msc_uma_to_gsm_succACCUMULATIONINT8Number of successful intra-MSC UMA GSM handovers.HO1.M81B3C121nkmtbh
intra_msc_uma_to_umts_dropACCUMULATIONINT8Number of calls dropped due to failed intra-MSC UMA-UMTS handovers.HO1.M81B3C128nkmtbh
intra_msc_uma_to_umts_failACCUMULATIONINT8Number of unsuccessful intra-MSC UMA UMTS handovers.HO1.M81B3C126nkmtbh
intra_msc_uma_to_umts_reestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC UMA-UMTSHO1.M81B3C127nkmtbh
intra_msc_uma_to_umts_succACCUMULATIONINT8Number of successful intra-MSC UMA UMTS handovers.HO1.M81B3C125nkmtbh
intra_msc_umts_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed intra-MSC UMTS-UMA handovers.HO1.M81B3C120nkmtbh
intra_msc_umts_to_uma_failACCUMULATIONINT8Number of unsuccessful intra-MSC UMTS-UMA handovers.HO1.M81B3C118nkmtbh
intra_msc_umts_to_uma_reestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC UMTS-UMA handovers.HO1.M81B3C119nkmtbh
intra_msc_umts_to_uma_succACCUMULATIONINT8Number of successful intra-MSC UMTS UMA handovers.HO1.M81B3C117nkmtbh


MSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN

Unlicenced mobile access Inter PLMN UMTS handover data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_out_inter_p_gsm_to_uma_failPERCENTAGEFLOATPercentage unsuccessful inter-PLMN GSM-UMA handovers.percentfail({out_inter_p_gsm_to_uma_fail}, ({out_inter_p_gsm_to_uma_succ} + {out_inter_p_gsm_to_uma_fail}))nkmtbh
%_out_inter_p_gsm_to_uma_succPERCENTAGEFLOATPercentage successful inter-PLMN GSM-UMA handovers.percentok({out_inter_p_gsm_to_uma_succ}, ({out_inter_p_gsm_to_uma_succ} + {out_inter_p_gsm_to_uma_fail}))nkmtbh
%_out_inter_p_uma_to_gsm_failPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN UMA-GSM handovers.percentfail({out_inter_p_uma_to_gsm_fail}, ({out_inter_p_uma_to_gsm_succ} + {out_inter_p_uma_to_gsm_fail}))nkmtbh
%_out_inter_p_uma_to_gsm_succPERCENTAGEFLOATPercentage successful outgoing inter-PLMN UMA-GSM handovers.percentok({out_inter_p_uma_to_gsm_succ}, ({out_inter_p_uma_to_gsm_succ} + {out_inter_p_uma_to_gsm_fail}))nkmtbh
%_out_inter_p_uma_to_umts_failPERCENTAGEFLOATPercentage unsuccessfull outgoing inter-PLMN UMA-UMTS handovers.percentfail({out_inter_p_uma_to_umts_fail}, ({out_inter_p_uma_to_umts_succ} + {out_inter_p_uma_to_umts_fail}))nkmtbh
%_out_inter_p_uma_to_umts_succPERCENTAGEFLOATPercentage successfull outgoing inter-PLMN UMA-UMTS handovers.percentok({out_inter_p_uma_to_umts_succ}, ({out_inter_p_uma_to_umts_succ} + {out_inter_p_uma_to_umts_fail}))nkmtbh
%_out_inter_p_umts_to_uma_failPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN UMTS-UMA handovers.percentfail({out_inter_p_umts_to_uma_fail}, ({out_inter_p_umts_to_uma_succ} + {out_inter_p_umts_to_uma_fail}))nkmtbh
%_out_inter_p_umts_to_uma_succPERCENTAGEFLOATPercentage successful outgoing inter-PLMN UMTS-UMA handovers.percentok({out_inter_p_umts_to_uma_succ}, ({out_inter_p_umts_to_uma_succ} + {out_inter_p_umts_to_uma_fail}))nkmtbh
dropped_callsACCUMULATIONINT8Dropped calls.{out_inter_p_gsm_to_uma_drop} + {out_inter_p_umts_to_uma_drop} + {out_inter_p_uma_to_gsm_drop} + {out_inter_p_uma_to_umts_drop}nkmtbh
out_inter_p_gsm_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN GSM-UMA handovers.HO1.M81B3C188nkmtbh
out_inter_p_gsm_to_uma_failACCUMULATIONINT8Number of unsuccessful outgoing inter- PLMN GSM-UMA handovers.HO1.M81B3C186nkmtbh
out_inter_p_gsm_to_uma_reestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN GSM-UMA handovers.HO1.M81B3C187nkmtbh
out_inter_p_gsm_to_uma_succACCUMULATIONINT8Number of successful outgoing inter- PLMN GSM-UMA handovers.HO1.M81B3C185nkmtbh
out_inter_p_uma_to_gsm_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN UMA-GSM handovers.HO1.M81B3C196nkmtbh
out_inter_p_uma_to_gsm_failACCUMULATIONINT8Number of unsuccessful outgoing inter- PLMN UMA-GSM handovers.HO1.M81B3C194nkmtbh
out_inter_p_uma_to_gsm_reestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN UMA-GSM handovers.HO1.M81B3C195nkmtbh
out_inter_p_uma_to_gsm_succACCUMULATIONINT8Number of successful outgoing inter- PLMN UMA-GSM handovers.HO1.M81B3C193nkmtbh
out_inter_p_uma_to_umts_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN UMA-UMTS handovers.HO1.M81B3C200nkmtbh
out_inter_p_uma_to_umts_failACCUMULATIONINT8Number of unsuccessful outgoing inter- PLMN UMA-UMTS handovers.HO1.M81B3C198nkmtbh
out_inter_p_uma_to_umts_reestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN UMA-UMTS handovers.HO1.M81B3C199nkmtbh
out_inter_p_uma_to_umts_succACCUMULATIONINT8Number of successful outgoing inter- PLMN UMA-UMTS handovers.HO1.M81B3C197nkmtbh
out_inter_p_umts_to_uma_dropACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN UMTS-UMA handovers.HO1.M81B3C192nkmtbh
out_inter_p_umts_to_uma_failACCUMULATIONINT8Number of unsuccessful outgoing inter- PLMN UMTS UMA handovers.HO1.M81B3C190nkmtbh
out_inter_p_umts_to_uma_reestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN UMTS-UMA handovers.HO1.M81B3C191nkmtbh
out_inter_p_umts_to_uma_succACCUMULATIONINT8Number of successful outgoing inter- PLMN UMTS-UMA handovers.HO1.M81B3C189nkmtbh


MSC.Nokia.GSM.UMTS_GSM_Handovers

This measurement contains the information about the number of the MSC and BSC controlled successful and unsuccessful handovers. Specifically UMTS - GSM

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_succ_i_msc_umts_gsm_hoPERCENTAGEFLOATPercentage successful intra-MSC UMTS-GSM handovers.percentok({succ_i_msc_umts_gsm_ho}, ({succ_i_msc_umts_gsm_ho} + {unsucc_i_msc_umts_gsm_ho}))nkmtbh
%_succ_inc_e_msc_umts_gsm_hoPERCENTAGEFLOATPercentage successful incoming inter-MSC UMTS-GSM handovers.percentok({succ_inc_e_msc_umts_gsm_ho}, ({succ_inc_e_msc_umts_gsm_ho} + {unsucc_inc_e_msc_umts_gsm_ho}))nkmtbh
%_succ_inc_e_plmn_umts_gsm_hoPERCENTAGEFLOATPercentage successful incoming inter-PLMN UMTS-GSM handovers.percentok({succ_inc_e_plmn_umts_gsm_ho}, ({succ_inc_e_plmn_umts_gsm_ho} + {unsucc_inc_e_plmn_umts_gsm_ho}))nkmtbh
%_succ_out_e_msc_umts_gsm_hoPERCENTAGEFLOATPercentage successful outgoing inter-MSC UMTS-GSM handovers.percentok({succ_out_e_msc_umts_gsm_ho}, ({succ_out_e_msc_umts_gsm_ho} + {unsucc_out_e_msc_umts_gsm_ho}))nkmtbh
%_succ_out_e_plmn_umts_gsm_hoPERCENTAGEFLOATPercentage successful outgoing inter-PLMN UMTS-GSM handovers.percentok({succ_out_e_plmn_umts_gsm_ho}, ({succ_out_e_plmn_umts_gsm_ho} + {unsucc_out_e_plmn_umts_gsm_ho}))nkmtbh
%_succ_plmn_msc_umts_gsm_hoPERCENTAGEFLOATPercentage successful inter-PLMN intra-MSC UMTS-GSM handovers.percentok({succ_plmn_msc_umts_gsm_ho}, ({succ_plmn_msc_umts_gsm_ho} + {unsucc_plmn_msc_umts_gsm_ho}))nkmtbh
%_unsucc_i_msc_umts_gsm_hoPERCENTAGEFLOATPercentage unsuccessful intra-MSC UMTS-GSM handovers.percentfail({unsucc_i_msc_umts_gsm_ho}, ({succ_i_msc_umts_gsm_ho} + {unsucc_i_msc_umts_gsm_ho}))nkmtbh
%_unsucc_inc_e_msc_umts_gsm_hoPERCENTAGEFLOATPercentage unsuccessful incoming inter-MSC UMTS-GSM handovers.percentfail({unsucc_inc_e_msc_umts_gsm_ho}, ({succ_inc_e_msc_umts_gsm_ho} + {unsucc_inc_e_msc_umts_gsm_ho}))nkmtbh
%_unsucc_inc_e_plmn_umts_gsm_hoPERCENTAGEFLOATPercentage unsuccessful incoming inter-PLMN UMTS-GSM handovers.percentfail({unsucc_inc_e_plmn_umts_gsm_ho}, ({succ_inc_e_plmn_umts_gsm_ho} + {unsucc_inc_e_plmn_umts_gsm_ho}))nkmtbh
%_unsucc_out_e_msc_umts_gsm_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-MSC UMTS-GSM handovers.percentfail({unsucc_out_e_msc_umts_gsm_ho}, ({succ_out_e_msc_umts_gsm_ho} + {unsucc_out_e_msc_umts_gsm_ho}))nkmtbh
%_unsucc_out_e_plmn_umts_gsm_hoPERCENTAGEFLOATPercentage unsuccessful outgoing inter-PLMN UMTS-GSM handovers.percentfail({unsucc_out_e_plmn_umts_gsm_ho}, ({succ_out_e_plmn_umts_gsm_ho} + {unsucc_out_e_plmn_umts_gsm_ho}))nkmtbh
%_unsucc_plmn_msc_umts_gsm_hoPERCENTAGEFLOATPercentage unsuccessful inter-PLMN intra-MSC UMTS-GSM handovers.percentfail({unsucc_plmn_msc_umts_gsm_ho}, ({succ_plmn_msc_umts_gsm_ho} + {unsucc_plmn_msc_umts_gsm_ho}))nkmtbh
dropped_callsACCUMULATIONINT8Dropped calls.{ieplmniamscumtstogsmclear} + {iniemscumtstogsmclear} + {outiemscumtstogsmclear} + {inieplmnumtstogsmclear} + {outieplmnumtstogsmclear}nkmtbh
iamscumtstogsmreestACCUMULATIONINT8Number of successful re-establishments in failed intra-MSC UMTS-GMS handoversHO1.M81B3C67nkmtbh
ieplmniamscumtstogsmclearACCUMULATIONINT8Number of calls dropped due to failed inter-PLMN intra-MSC UMTS-GSM handoversHO1.M81B3C76nkmtbh
ieplmniamscumtstogsmreestACCUMULATIONINT8Number of successful re-establishments in failed inter-PLMN intra- MSC UMTSGSM handoversHO1.M81B3C75nkmtbh
iniemscumtstogsmclearACCUMULATIONINT8Number of calls dropped due to failed inter-MSC UMTS-GSM handoversHO1.M81B3C84nkmtbh
inieplmnumtstogsmclearACCUMULATIONINT8Number of calls dropped due to failed incoming inter-PLMN inter-MSC UMTSGSM handoversHO1.M81B3C100nkmtbh
outiemscumtstogsmclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-MSC UMTS- GSM handoversHO1.M81B3C92nkmtbh
outiemscumtstogsmreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-MSC UMTS-GSM handoversHO1.M81B3C91nkmtbh
outieplmnumtstogsmclearACCUMULATIONINT8Number of calls dropped due to failed outgoing inter-PLMN inter-MSC UMTSGSM handoversHO1.M81B3C108nkmtbh
outieplmnumtstogsmreestACCUMULATIONINT8Number of successful re-establishments in failed outgoing inter-PLMN inter-MSC UMTS-GSM handoversHO1.M81B3C107nkmtbh
succ_i_msc_umts_gsm_hoACCUMULATIONINT8The number of successful intra-MSC UMTS-GSM handovers. HO1.M81B3C9nkmtbh
succ_inc_e_msc_umts_gsm_hoACCUMULATIONINT8The number of successful incoming inter-MSC UMTS-GSM handovers. HO1.M81B3C19nkmtbh
succ_inc_e_plmn_umts_gsm_hoACCUMULATIONINT8The number of successful incoming inter-PLMN UMTS-GSM handovers. HO1.M81B3C37nkmtbh
succ_out_e_msc_umts_gsm_hoACCUMULATIONINT8The number of successful outgoing inter-MSC UMTS-GSM handovers. HO1.M81B3C29nkmtbh
succ_out_e_plmn_umts_gsm_hoACCUMULATIONINT8The number of successful outgoing inter-PLMN UMTS-GSM handovers. HO1.M81B3C45nkmtbh
succ_plmn_msc_umts_gsm_hoACCUMULATIONINT8The number of successful inter- PLMN intra-MSC UMTS-GSM handovers. HO1.M81B3C53nkmtbh
unsucc_i_msc_umts_gsm_hoACCUMULATIONINT8The number of unsuccessful intra-MSC UMTS-GSM handovers. HO1.M81B3C10nkmtbh
unsucc_inc_e_msc_umts_gsm_hoACCUMULATIONINT8The number of unsuccessful incoming inter-MSC UMTS-GSM handovers. HO1.M81B3C20nkmtbh
unsucc_inc_e_plmn_umts_gsm_hoACCUMULATIONINT8The number of unsuccessful incoming inter-PLMN UMTS-GSM handovers. HO1.M81B3C38nkmtbh
unsucc_out_e_msc_umts_gsm_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-MSC UMTS-GSM handovers. HO1.M81B3C30nkmtbh
unsucc_out_e_plmn_umts_gsm_hoACCUMULATIONINT8The number of unsuccessful outgoing inter-PLMN UMTS-GSM handovers. HO1.M81B3C46nkmtbh
unsucc_plmn_msc_umts_gsm_hoACCUMULATIONINT8The number of unsuccessful inter- PLMN intra-MSC UMTS-GSM handovers. HO1.M81B3C54nkmtbh


MSC_CAP_Application_Context Performance Indicators

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


MSC_CAP_Application_Context.Nokia.GSM.Session

CAP Application context sessions

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_ABORT_CAP_ACPERCENTAGEFLOATPercentage abortspercentok(({CAP_AC_USER_ABORT} + {CAP_AC_INTERNAL_ABORT} + {CAP_AC_TCAP_USER_ABORT} + {CAP_AC_TCAP_PROVIDER_ABORT} + {CAP_AC_CANCELLED} + {CAP_AC_TIMER_EXPIRATION}), {CAP_AC_STARTED})nkmtbh
CAP_AC_CANCELLEDACCUMULATIONINT8The number of application context interruptions caused by the expiration of TCAP time supervision during the measurement period.CAPMDAC.M200B11C6 or CAPMSAC.M200B11C6nkmtbh
CAP_AC_INTERNAL_ABORTACCUMULATIONINT8The number of application contexts aborted by the CAP itself during the measurement period.CAPMDAC.M200B11C3 or CAPMSAC.M200B11C3nkmtbh
CAP_AC_STARTEDACCUMULATIONINT8The number of started CAP application contexts during the measurement period.CAPMDAC.M200B11C1 or CAPMSAC.M200B11C1nkmtbh
CAP_AC_TCAP_PROVIDER_ABORTACCUMULATIONINT8The number of application contexts aborted by the TCAP in the SSF or SCF during the measurement period.CAPMDAC.M200B11C5 or CAPMSAC.M200B11C5nkmtbh
CAP_AC_TCAP_USER_ABORTACCUMULATIONINT8The number of application contexts aborted by the receiving CAP entity during the measurement period.CAPMDAC.M200B11C4 or CAPMSAC.M200B11C4nkmtbh
CAP_AC_TIMER_EXPIRATIONACCUMULATIONINT8The number of application context interruptions caused by the expiration of CAP internal time supervision during the measurement period.CAPMDAC.M200B11C7 or CAPMSAC.M200B11C7nkmtbh
CAP_AC_USER_ABORTACCUMULATIONINT8The number of application contexts aborted by the CAP user during the measurement period.CAPMDAC.M200B11C2 or CAPMSAC.M200B11C2nkmtbh
TOTAL_CAP_AC_ABORTACCUMULATIONINT8The total number of application contexts aborted during the measurement period.{CAP_AC_USER_ABORT} + {CAP_AC_INTERNAL_ABORT} + {CAP_AC_TCAP_USER_ABORT} + {CAP_AC_TCAP_PROVIDER_ABORT} + {CAP_AC_CANCELLED} + {CAP_AC_TIMER_EXPIRATION}nkmtbh


MSC_Destination Performance Indicators

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


MSC_Destination.Nokia.GSM.CAP_Invocation

CAP Invocations

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_DP_DATA_PROV_RESTARTINTENSITYFLOATShows whether the signalling units or the program blocks inside them that provide counters to the measurement were restarted during the measurement period and thus data might be missing from the measurement.CAPMDEST.M200B7C1 or CAPMSN.M200B7C1nkmtbh
CAP_DP_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed CAP invocations during the measurement period.CAPMDEST.M200B7C4 or CAPMSN.M200B7C4nkmtbh
CAP_DP_SUM_STARTEDACCUMULATIONINT8Shows the total number of started CAP invocations during the measurement period.CAPMDEST.M200B7C3 or CAPMSN.M200B7C3nkmtbh


MSC_Destination.Nokia.GSM.CAP_Reject_cause

CAP operation rejects

The performance data measurements for this KPI group are recorded against the combination of MSC_Destination and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_OC_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.CAPMDRC.M200B10C1 or CAPMSRC.M200B10C1nkmtbh


MSC_Destination.Nokia.GSM.INAP_Incoming_App_Context

INAP Incoming Application Context

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_IAC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful incoming INAP application contexts during the measurement period.percentok(({INAP_IAC_SUM_STARTED} - {INAP_IAC_SUM_FAILED}), ({INAP_IAC_SUM_SUCCEEDED}))nkmtbh
INAP_IAC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement during the measurement period had been restarted, and thus data might be missing from the measurement.IACIMDES.M196B1C1 or IACIMSN.M196B1C1nkmtbh
INAP_IAC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming INAP application contexts during the measurement period.IACIMDES.M196B1C5 or IACIMSN.M196B1C5nkmtbh
INAP_IAC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming INAP application contexts during the measurement period.IACIMDES.M196B1C3 or IACIMSN.M196B1C3nkmtbh
INAP_IAC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming INAP application contexts during the measurement period.IACIMDES.M196B1C4 or IACIMSN.M196B1C4nkmtbh


MSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part1

INAP Incoming Operation Code report part1

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC1_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement during the measurement period, had been restarted and thus data might be missing from the measurement.IOC1MDES.M193B1C1 or IOC1MSN.M193B1C1nkmtbh
INAP_IOC1_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming INAP operations (in the report part) during the measurement period.IOC1MDES.M193B1C5 or IOC1MSN.M193B1C5nkmtbh
INAP_IOC1_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming INAP operations (in the report part) during the measurement period.IOC1MDES.M193B1C3 or IOC1MSN.M193B1C3nkmtbh
INAP_IOC1_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming INAP operations (in the report part) during the measurement period.IOC1MDES.M193B1C4 or IOC1MSN.M193B1C4nkmtbh


MSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part2

INAP Incoming Operation Code report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.IOC2MDES.M194B1C1 or IOC2MSN.M194B1C1nkmtbh
INAP_IOC2_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming INAP operations (in the report part) during the measurement period.IOC2MDES.M194B1C5 or IOC2MSN.M194B1C5nkmtbh
INAP_IOC2_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming INAP operations (in the report part) during the measurement period.IOC2MDES.M194B1C3 or IOC2MSN.M194B1C3nkmtbh
INAP_IOC2_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming INAP operations (in the report part) during the measurement period.IOC2MDES.M194B1C4 or IOC2MSN.M194B1C4nkmtbh


MSC_Destination.Nokia.GSM.INAP_Incoming_Reject_Cause

INAP Incoming operation rejects

The performance data measurements for this KPI group are recorded against the combination of MSC_Destination and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.IOC2MDRC.M194B5C1 or IOC2MSRC.M194B5C1nkmtbh


MSC_Destination.Nokia.GSM.INAP_Invocation

INAP detection point Invocation

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_DP_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement during the measurement period had been restarted and thus data might be missing from the measurement.IDPMDES.M199B1C1 or IDPMSN.M199B1C1nkmtbh
INAP_DP_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed INAP invocations during the measurement period.IDPMDES.M199B1C4 or IDPMSN.M199B1C4nkmtbh
INAP_DP_SUM_STARTEDACCUMULATIONINT8Shows the total number of started INAP invocations during the measurement period.IDPMDES.M199B1C3 or IDPMSN.M199B1C3nkmtbh


MSC_Destination.Nokia.GSM.INAP_Outgoing_App_Context

INAP Outgoing Application Context

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_OAC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful outgoing INAP application contexts during the measurement period.percentok(({INAP_OAC_SUM_STARTED} - {INAP_OAC_SUM_FAILED}), ({INAP_OAC_SUM_SUCCEEDED}))nkmtbh
INAP_OAC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.IACOMDES.M197B1C1 or IACOMSN.M197B1C1nkmtbh
INAP_OAC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed outgoing INAP application contexts during the measurement period.IACOMDES.M197B1C5 or IACOMSN.M197B1C5nkmtbh
INAP_OAC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started outgoing INAP application contexts during the measurement period.IACOMDES.M197B1C3 or IACOMSN.M197B1C3nkmtbh
INAP_OAC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded outgoing INAP application contexts during the measurement period.IACOMDES.M197B1C4 or IACOMSN.M197B1C4nkmtbh


MSC_Destination.Nokia.GSM.INAP_Outgoing_Op_Code

INAP Outgoing Operations Code

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_INAP_OOC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful outgoing INAP operations during the measurement period.percentok(({INAP_OOC_SUM_STARTED} - {INAP_OOC_SUM_FAILED}), ({INAP_OOC_SUM_SUCCEEDED}))nkmtbh
INAP_OOC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period and thus data might be missing from the measurement.IOCOMDES.M195B1C1 or IOCOMSN.M195B1C1nkmtbh
INAP_OOC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed outgoing INAP operations during the measurement period.IOCOMDES.M195B1C5 or IOCOMSN.M195B1C5nkmtbh
INAP_OOC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started outgoing INAP operations during the measurement period.IOCOMDES.M195B1C3 or IOCOMSN.M195B1C3nkmtbh
INAP_OOC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded outgoing INAP operations during the measurement period.IOCOMDES.M195B1C4 or IOCOMSN.M195B1C4nkmtbh


MSC_Destination.Nokia.GSM.INAP_Outgoing_Reject_Cause

INAP Outgoing Operation rejects

The performance data measurements for this KPI group are recorded against the combination of MSC_Destination and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OOC_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.IOCOMDRC.M195B5C1 or IOCOMSRC.M195B5C1nkmtbh


MSC_Destination.Nokia.GSM.Incoming_CAP_Application_Context

CAP Incoming Application Context

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_CAP_IAC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful incoming CAP application contexts during the measurement period.percentok(({CAP_IAC_SUM_STARTED} - {CAP_IAC_SUM_FAILED}), ({CAP_IAC_SUM_SUCCEEDED}))nkmtbh
CAP_IAC_DATA_PROV_RESTARTINTENSITYFLOATShows whether the signalling units or the program blocks inside them that provide counters to the measurement during the measurement period were restarted and thus data might be missing from the measurement.CAPMDEST.M200B5C1 or CAPMSN.M200B5C1nkmtbh
CAP_IAC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming CAP application contexts during the measurement period.CAPMDEST.M200B5C5 or CAPMSN.M200B5C5nkmtbh
CAP_IAC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming CAP application contexts during the measurement period.CAPMDEST.M200B5C3 or CAPMSN.M200B5C3nkmtbh
CAP_IAC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of successful incoming CAP application contexts during the measurement period.CAPMDEST.M200B5C4 or CAPMSN.M200B5C4nkmtbh


MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1

CAP Incoming Operations report Part 1

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_IOC1_DATA_PROV_RESTARTINTENSITYINT8Shows whether the signalling units or program blocks inside them that provide counters to the measurement were restarted during the measurement period and thus data may be missing from the measurement.CAPMDEST.M200B1C1 or CAPMSN.M200B1C1nkmtbh
CAP_IOC1_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B1C5 or CAPMSN.M200B1C5nkmtbh
CAP_IOC1_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B1C3 or CAPMSN.M200B1C3nkmtbh
CAP_IOC1_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B1C4 or CAPMSN.M200B1C4nkmtbh


MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2

CAP Incoming Operations report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_IOC2_DATA_PROV_RESTARTINTENSITYFLOATShows whether the signalling units or program blocks inside them that provide counters to the measurement were restarted during the measurement period and thus data may be missing from the measurement.CAPMDEST.M200B2C1 or CAPMSN.M200B2C1nkmtbh
CAP_IOC2_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B2C5 or CAPMSN.M200B2C5nkmtbh
CAP_IOC2_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B2C3 or CAPMSN.M200B2C3nkmtbh
CAP_IOC2_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B2C4 or CAPMSN.M200B2C4nkmtbh


MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3

Incoming CAP Operations report part 3

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_SUCC_CAP_IOC_TOTALPERCENTAGEFLOATPercentage successful CAP Operations for all 3 report parts.percentok(({MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1.CAP_IOC1_SUM_SUCCEEDED} + {MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2.CAP_IOC2_SUM_SUCCEEDED} + {CAP_IOC3_SUM_SUCCEEDED}), ({MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1.CAP_IOC1_SUM_STARTED} + {MSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2.CAP_IOC2_SUM_STARTED} + {CAP_IOC3_SUM_STARTED}))nkmtbh
CAP_IOC3_DATA_PROV_RESTARTINTENSITYFLOATShows whether the signalling units or program blocks inside them that provide counters to the measurement were restarted during the measurement period and thus data may be missing from the measurement.CAPMDEST.M200B3C1 or CAPMSN.M200B3C1nkmtbh
CAP_IOC3_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B3C5 or CAPMSN.M200B3C5nkmtbh
CAP_IOC3_SUM_STARTEDACCUMULATIONINT8Shows the total number of started incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B3C3 or CAPMSN.M200B3C3nkmtbh
CAP_IOC3_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded incoming CAP operations (in the report part) during the measurement period.CAPMDEST.M200B3C4 or CAPMSN.M200B3C4nkmtbh


MSC_Destination.Nokia.GSM.Outgoing_CAP_Application_Context

CAP Outgoing Application Context

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_CAP_OAC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful outgoing CAP application contexts during the measurement period.percentok(({CAP_OAC_SUM_STARTED} - {CAP_OAC_SUM_FAILED}), ({CAP_OAC_SUM_SUCCEEDED}))nkmtbh
CAP_OAC_DATA_PROV_RESTARTINTENSITYFLOATShows whether any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.CAPMDEST.M200B6C1 or CAPMSN.M200B6C1nkmtbh
CAP_OAC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed outgoing CAP application contexts during the measurement period.CAPMDEST.M200B6C5 or CAPMSN.M200B6C5nkmtbh
CAP_OAC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started outgoing CAP application contexts during the measurement period.CAPMDEST.M200B6C3 or CAPMSN.M200B6C3nkmtbh
CAP_OAC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded outgoing CAP application contexts during the measurement period.CAPMDEST.M200B6C4 or CAPMSN.M200B6C4nkmtbh


MSC_Destination.Nokia.GSM.Outgoing_CAP_Operation

CAP Outgoing Operations

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_CAP_OOC_SUCCEEDEDPERCENTAGEFLOATShows the percentage of successful outgoing CAP operations during the measurement period.percentok(({CAP_OOC_SUM_STARTED} - {CAP_OOC_SUM_FAILED}), ({CAP_OOC_SUM_SUCCEEDED}))nkmtbh
CAP_OOC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.CAPMDEST.M200B4C1 or CAPMSN.M200B4C1nkmtbh
CAP_OOC_SUM_FAILEDACCUMULATIONINT8Shows the total number of failed outgoing CAP operations during the measurement period.CAPMDEST.M200B4C5 or CAPMSN.M200B4C5nkmtbh
CAP_OOC_SUM_STARTEDACCUMULATIONINT8Shows the total number of started outgoing CAP operations during the measurement period.CAPMDEST.M200B4C3 or CAPMSN.M200B4C3nkmtbh
CAP_OOC_SUM_SUCCEEDEDACCUMULATIONINT8Shows the total number of succeeded outgoing CAP operations during the measurement period.CAPMDEST.M200B4C4 or CAPMSN.M200B4C4nkmtbh


MSC_Destination.Nokia.GSM.SSAP_Dialogue

SSAP Dialogue

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_DI_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.SSAPMSUB.M198B1C1nkmtbh
SSAP_DI_SUM_FAILED_INACCUMULATIONINT8Shows the total number of failed incoming SSAP dialogues during the measurement period.SSAPMSUB.M198B1C5nkmtbh
SSAP_DI_SUM_FAILED_OUTACCUMULATIONINT8Shows the total number of failed outgoing SSAP dialogues during the measurement period.SSAPMSUB.M198B1C6nkmtbh
SSAP_DI_SUM_STARTED_INACCUMULATIONINT8Shows the total number of started incoming SSAP dialogues during the measurement period.SSAPMSUB.M198B1C3nkmtbh
SSAP_DI_SUM_STARTED_OUTACCUMULATIONINT8Shows the total number of started outgoing SSAP dialogues during the measurement period.SSAPMSUB.M198B1C4nkmtbh


MSC_Destination.Nokia.GSM.SSAP_Operation_Code

SSAP Operation codes

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_SSAP_OC_SUCCEEDED_OUTPERCENTAGEFLOATShows the percentage of successful outgoing SSAP operations during the measurement period.percentok(({SSAP_OC_SUM_STARTED_IN} + {SSAP_OC_SUM_STARTED_OUT} - {SSAP_OC_SUM_FAILED_IN} - {SSAP_OC_SUM_FAILED_IN}), ({SSAP_OC_SUM_STARTED_IN} + {SSAP_OC_SUM_STARTED_OUT}))nkmtbh
SSAP_OC_DATA_PROV_RESTARTINTENSITYFLOATShows that any of the signalling units or program blocks inside them that provide counters to the measurement had been restarted during the measurement period, and thus data might be missing from the measurement.SSAPMSUB.M198B0C1nkmtbh
SSAP_OC_SUM_FAILED_INACCUMULATIONINT8Shows the total number of failed incoming SSAP operations during the measurement period.SSAPMSUB.M198B0C5nkmtbh
SSAP_OC_SUM_FAILED_OUTACCUMULATIONINT8Shows the total number of failed outgoing SSAP operations during the measurement period.SSAPMSUB.M198B0C6nkmtbh
SSAP_OC_SUM_STARTED_INACCUMULATIONINT8Shows the total number of started incoming SSAP operations during the measurement period.SSAPMSUB.M198B0C3nkmtbh
SSAP_OC_SUM_STARTED_OUTACCUMULATIONINT8Shows the total number of started outgoing SSAP operations during the measurement period.SSAPMSUB.M198B0C4nkmtbh


MSC_Destination.Nokia.GSM.SSAP_Reject

SSAP operation rejects

The performance data measurements for this KPI group are recorded against the combination of MSC_Destination and Reject_Cause (reject_cause_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_RC_NUMBERACCUMULATIONINT8Shows the number of reject causes during the measurement period.SSAPMSRC.M198B5C1nkmtbh


MSC_Detection_Point Performance Indicators

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


MSC_Detection_Point.Nokia.GSM.CAP_Service_Invocation

CAP Detection Point Invocations

The performance data measurements for this KPI group are recorded against the combination of MSC_Detection_Point and IN_Service (in_service_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_SUCC_CAP_DP_INVOCATIONSPERCENTAGEFLOATPercentage success failed service keys during the measurement period.percentok(({CAP_DP_STARTED_INVOCATIONS} - {CAP_DP_FAILED_INVOCATIONS}), ({CAP_DP_STARTED_INVOCATIONS})) 
CAP_DP_FAILED_INVOCATIONSACCUMULATIONINT8The number of failed service keys during the measurement period.CAPMD.M200B13C2 or CAPMS.M200B13C2nkmtbh
CAP_DP_STARTED_INVOCATIONSACCUMULATIONINT8The number of started service keys during the measurement period.CAPMD.M200B13C1 or CAPMS.M200B13C1nkmtbh


MSC_Detection_Point.Nokia.GSM.INAP_Service_Invocation

INAP Service Detection Point Invocations

The performance data measurements for this KPI group are recorded against the combination of MSC_Detection_Point and IN_Service (in_service_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_DP_FAILED_INVOCATIONSACCUMULATIONINT8Shows the number of failed service keys during the measurement period.IDPMD.M199B3C2 or IDPMS.M199B3C2nkmtbh
INAP_DP_STARTED_INVOCATIONSACCUMULATIONINT8Shows the number of started service keys during the measurement period.IDPMD.M199B3C1 or IDPMS.M199B3C1nkmtbh


MSC_INAP_Application_Context Performance Indicators

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


MSC_INAP_Application_Context.Nokia.GSM.Incoming_Session

INAP Incoming Application Context

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IAC_ABORT_TOTALACCUMULATIONINT8Shows the number of application context interruptions during the measurement period.{INAP_IAC_USER_ABORT} + {INAP_IAC_INTERNAL_ABORT} + {INAP_IAC_TCAP_USER_ABORT} + {INAP_IAC_TCAP_PROVIDER_ABORT} + {INAP_IAC_CANCELLED} + {INAP_IAC_TIMER_EXPIRATION}nkmtbh
INAP_IAC_CANCELLEDACCUMULATIONINT8Shows the number of application context interruptions caused by TCAP time supervision expiration during the measurement period.IACIMDAC.M196B3C6 or IACIMSAC.M196B3C6nkmtbh
INAP_IAC_INTERNAL_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by INAP itself during the measurement period.IACIMDAC.M196B3C3 or IACIMSAC.M196B3C3nkmtbh
INAP_IAC_STARTEDACCUMULATIONINT8Shows the number of started INAP application contexts during the measurement period.IACIMDAC.M196B3C1 or IACIMSAC.M196B3C1nkmtbh
INAP_IAC_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the TCAP in the SSP or SCP during the measurement period.IACIMDAC.M196B3C5 or IACIMSAC.M196B3C5nkmtbh
INAP_IAC_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the receiving INAP entity during the measurement period.IACIMDAC.M196B3C4 or IACIMSAC.M196B3C4nkmtbh
INAP_IAC_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of application context interruptions caused by the expiration of INAP internal time supervision during the measurement period.IACIMDAC.M196B3C7 or IACIMSAC.M196B3C7nkmtbh
INAP_IAC_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the INAP user during the measurement period.IACIMDAC.M196B3C2 or IACIMSAC.M196B3C2nkmtbh


MSC_INAP_Application_Context.Nokia.GSM.Outgoing_Session

INAP Outgoing Application Context

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OAC_ABORT_TOTALACCUMULATIONINT8Shows the number of application context interruptions during the measurement period.{INAP_OAC_USER_ABORT} + {INAP_OAC_INTERNAL_ABORT} + {INAP_OAC_TCAP_USER_ABORT} + {INAP_OAC_TCAP_PROVIDER_ABORT} + {INAP_OAC_CANCELLED} + {INAP_OAC_TIMER_EXPIRATION}nkmtbh
INAP_OAC_CANCELLEDACCUMULATIONINT8Shows the number of application context interruptions caused by the expiration of TCAP time supervision during the measurement period.IACOMDAC.M197B3C6 or IACOMSAC.M197B3C6nkmtbh
INAP_OAC_INTERNAL_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the INAP itself during the measurement period.IACOMDAC.M197B3C3 or IACOMSAC.M197B3C3nkmtbh
INAP_OAC_STARTEDACCUMULATIONINT8Shows the number of started INAP application contexts during the measurement period.IACOMDAC.M197B3C1 or IACOMSAC.M197B3C1nkmtbh
INAP_OAC_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the TCAP in the SSP or SCP during the measurement period.IACOMDAC.M197B3C5 or IACOMSAC.M197B3C5nkmtbh
INAP_OAC_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the receiving INAP entity during the measurement period.IACOMDAC.M197B3C4 or IACOMSAC.M197B3C4nkmtbh
INAP_OAC_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of application context interruptions caused by the expiration of INAP internal time supervision during the measurement period.IACOMDAC.M197B3C7 or IACOMSAC.M197B3C7nkmtbh
INAP_OAC_USER_ABORTACCUMULATIONINT8Shows the number of application contexts aborted by the INAP user during the measurement period.IACOMDAC.M197B3C2 or IACOMSAC.M197B3C2nkmtbh


MSC_INAP_Error_Code Performance Indicators

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


MSC_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part1

INAP Incoming terminations report part 1

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC1_EC_NUMBERACCUMULATIONINT8The number of INAP operations terminated due to error during the measurement period.IOC1MDEC.M193B4C1 or IOC1MSEC.M193B4C1nkmtbh


MSC_INAP_Error_Code.Nokia.GSM.Incoming_Termination_Part2

INAP Incoming terminations report part 2

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_EC_NUMBERACCUMULATIONINT8Shows the number of INAP operations terminated due to an error during the measurement period.IOC2MSEC.M194B4C1 or IOC2MDEC.M194B4C1nkmtbh


MSC_INAP_Error_Code.Nokia.GSM.Outgoing_Termination

INAP Outgoing terminations report

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OOC_EC_NUMBERACCUMULATIONINT8Shows the number of INAP operations terminated due to error during the measurement period.IOCOMDEC.M195B4C1 or IOCOMSEC.M195B4C1nkmtbh


MSC_INAP_Op_Code Performance Indicators

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


MSC_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part1

Incoming INAP Operations part 1

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC1_ABORTEDACCUMULATIONINT8Shows TCAP user,the number of aborted INAP operations due to internal errors or provider aborts during the measurement period.IOC1MDOC.M193B3C3 or IOC1MSOC.M193B3C3nkmtbh
INAP_IOC1_CANCELLEDACCUMULATIONINT8Shows the number of INAP operations cancelled due to timer expirations on different levels during the measurement period.IOC1MDOC.M193B3C5 or IOC1MSOC.M193B3C5nkmtbh
INAP_IOC1_ERRORSACCUMULATIONINT8Shows the number of INAP operations terminated by an error during the measurement period.IOC1MDOC.M193B3C2 or IOC1MSOC.M193B3C2nkmtbh
INAP_IOC1_REJECTEDACCUMULATIONINT8Shows the rejected INAP operations during the measurement period. It can be rejected by TCAP user of the remote end, by TCAP of the remote end, or by the near end TCAP.IOC1MDOC.M193B3C4 or IOC1MSOC.M193B3C4nkmtbh
INAP_IOC1_STARTEDACCUMULATIONINT8Shows the number of started INAP operations during the measurement period.IOC1MDOC.M193B3C1 or IOC1MSOC.M193B3C1nkmtbh


MSC_INAP_Op_Code.Nokia.GSM.Incoming_Session_Part2

Incoming INAP Operations part2

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IOC2_ABORTEDACCUMULATIONINT8Shows the TCAP user, the number of aborted INAP operations due to internal errors or provider aborts during the measurement period.IOC2MDOC.M194B3C3 or IOC2MSOC.M194B3C3nkmtbh
INAP_IOC2_CANCELLEDACCUMULATIONINT8Shows the number of INAP operations cancelled due to timer expirations on different levels during the measurement period.IOC2MDOC.M194B3C5 or IOC2MSOC.M194B3C5nkmtbh
INAP_IOC2_ERRORSACCUMULATIONINT8Shows the number of INAP operations terminated by an error during the measurement period.IOC2MDOC.M194B3C2 or IOC2MSOC.M194B3C2nkmtbh
INAP_IOC2_REJECTEDACCUMULATIONINT8Shows the rejected INAP operations during the measurement period. It can be rejected by TCAP user of the remote end, by TCAP of the remote end, or by the near end TCAP.IOC2MDOC.M194B3C4 or IOC2MSOC.M194B3C4nkmtbh
INAP_IOC2_STARTEDACCUMULATIONINT8Shows the number of started INAP operations during the measurement period.IOC2MDOC.M194B3C1 or IOC2MSOC.M194B3C1nkmtbh


MSC_INAP_Op_Code.Nokia.GSM.Outgoing_Session

Outgoing INAP Operations

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OOC_ABORTEDACCUMULATIONINT8Shows the TCAP user, the number of aborted INAP operations due to internal errors or provider aborts during the measurement period.IOCOMDOC.M195B3C3 or IOCOMSOC.M195B3C3nkmtbh
INAP_OOC_CANCELLEDACCUMULATIONINT8Shows the number of INAP operations cancelled due to timer expirations on different levels during the measurement period.IOCOMDOC.M195B3C5 or IOCOMSOC.M195B3C5nkmtbh
INAP_OOC_ERRORSACCUMULATIONINT8Shows the number of INAP operations terminated by an error during the measurement period.IOCOMDOC.M195B3C2 or IOCOMSOC.M195B3C2nkmtbh
INAP_OOC_REJECTEDACCUMULATIONINT8Shows the rejected INAP operations during the measurement period. It can be rejected by TCAP user of the remote end, by the TCAP of the remote end, or by the near end TCAP.IOCOMDOC.M195B3C4 or IOCOMSOC.M195B3C4nkmtbh
INAP_OOC_STARTEDACCUMULATIONINT8Shows the number of started INAP operations during the measurement period.IOCOMDOC.M195B3C1 or IOCOMSOC.M195B3C1nkmtbh


MSC_SSAP_Dialogue Performance Indicators

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


MSC_SSAP_Dialogue.Nokia.GSM.Session

SSAP Dialogue

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_DI_CANCELLEDACCUMULATIONINT8Shows the number of cancelled SSAP dialogues (interruptions caused by the expiration of TCAP time supervision) during the measurement period.SSAPMSDI.M198B6C5nkmtbh
SSAP_DI_OWN_ABORTACCUMULATIONINT8Shows the number of SSAP dialogues aborted by the SSAP itself during the measurement period.SSAPMSDI.M198B6C2nkmtbh
SSAP_DI_STARTEDACCUMULATIONINT8Shows the number of started SSAP dialogues during the measurement period.SSAPMSDI.M198B6C1nkmtbh
SSAP_DI_TCAP_PROVIDER_ABORTACCUMULATIONINT8Shows the number of SSAP dialogues aborted by the TCAP in the source or destination network element during the measurement period.SSAPMSDI.M198B6C4nkmtbh
SSAP_DI_TCAP_USER_ABORTACCUMULATIONINT8Shows the number of SSAP dialogues aborted by the receiving SSAP entity during the measurement period.SSAPMSDI.M198B6C3nkmtbh
SSAP_DI_TIMER_EXPIRATIONACCUMULATIONINT8Shows the number of interrupted SSAP dialogues caused by the expiration of SSAP internal time supervision during the measurement period.SSAPMSDI.M198B6C6nkmtbh


MSC_SSAP_Operation Performance Indicators

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


MSC_SSAP_Operation.Nokia.GSM.Session

SSAP Operation code

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_OC_ABORTEDACCUMULATIONINT8Shows the number of aborted SSAP operations due to internal errors or due to TCAP user or provider aborts during the measurement period.SSAPMSOC.M198B4C11nkmtbh
SSAP_OC_CANCELLEDACCUMULATIONINT8Shows the number of cancelled SSAP operations during the measurement period (number of operations cancelled due to timer expirations on different levels).SSAPMSOC.M198B4C13nkmtbh
SSAP_OC_CAUSED_BY_T3ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T3 during the measurement period.The maximum time, the service was available in the originating network, is expired.SSAPMSOC.M198B4C2nkmtbh
SSAP_OC_CAUSED_BY_T4ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T4 during the measurement period.The maximum time that the originating network waits for user A to respond to a CCBS or CCNR recall, is expired.SSAPMSOC.M198B4C3nkmtbh
SSAP_OC_CAUSED_BY_T7ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T7 during the measurement period.The lifetime of CCBS or CCNR request expired in the destination network.SSAPMSOC.M198B4C4nkmtbh
SSAP_OC_CAUSED_BY_T9ACCUMULATIONINT8Shows the number of SSAP operations resulted in an error caused by T9 during the measurement period.The maximum time, destination B waits for the CCBS call, when destination B has sent indication of remoteUserFree to the originating destination is expired.SSAPMSOC.M198B4C5nkmtbh
SSAP_OC_ERRORSACCUMULATIONINT8Shows the number of SSAP operations with an error result during the measurement period. The detailed error reason is also presented where applicable. Errors can occur on application level, or on the application protocol level, or they can indicate a negative result.SSAPMSOC.M198B4C7nkmtbh
SSAP_OC_LONG_TERM_DENIALACCUMULATIONINT8Shows the number of SSAP operations rejected because of LongTermDenial during the measurement period.The request to activate CCBS or CCNR has been rejected and most likely other following requests towards the same target user will be rejected.SSAPMSOC.M198B4C9nkmtbh
SSAP_OC_REJECTEDACCUMULATIONINT8Shows the number of rejected SSAP operations during the measurement period. The operations can be rejected by the TCAP user of the remote end, by the TCAP of the remote end or by the near end TCAP.SSAPMSOC.M198B4C12nkmtbh
SSAP_OC_SHORT_TERM_DENIALACCUMULATIONINT8Shows the number of SSAP operations rejected because of ShortTermDenial during the measurement period.The request to activate CCBS or CCNR has been rejected but the activation might be possible later.SSAPMSOC.M198B4C8nkmtbh
SSAP_OC_STARTEDACCUMULATIONINT8Shows the number of started SSAP operations during the measurement period.SSAPMSOC.M198B4C1nkmtbh
SSAP_OC_UNKNOWN_CAUSEACCUMULATIONINT8Shows the number of SSAP operations resulted in an error by unknown cause during the measurement period.SSAPMSOC.M198B4C6nkmtbh
SSAP_OC_UNKNOWN_ERRORACCUMULATIONINT8Shows the number of SSAP operations resulted in an unknown error during the measurement period.SSAPMSOC.M198B4C10nkmtbh


MSC_SSAP_Provider_Abort Performance Indicators

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


MSC_SSAP_Provider_Abort.Nokia.GSM.Session

SSAP Provider Abort

KPITypeData TypeDescriptionDerivationAdditional Summaries
SSAP_PA_NUMBERACCUMULATIONINT8Shows the number of TCAP provider aborts during the measurement period.SSAPMSPA.M198B7C1nkmtbh


MSC_TCAP_Provider_Abort Performance Indicators

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


MSC_TCAP_Provider_Abort.Nokia.GSM.CAP_Provider_Abort

CAP Provider Aborts

KPITypeData TypeDescriptionDerivationAdditional Summaries
CAP_AC_PA_NUMBERACCUMULATIONINT8The number of TCAP provider aborts during the measurement period.CAPMDPA.M200B12C1 or CAPMSPA.M200B12C1nkmtbh


MSC_TCAP_Provider_Abort.Nokia.GSM.INAP_Incoming_Provider_Abort

INAP Incoming Provider Abort

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_IAC_PA_NUMBERACCUMULATIONINT8Shows the number of TCAP provider aborts during the measurement period.IACIMDPA.M196B4C1 or IACIMSPA.M196B4C1nkmtbh


MSC_TCAP_Provider_Abort.Nokia.GSM.INAP_Outgoing_Provider_Abort

INAP Incoming Provider Abort

KPITypeData TypeDescriptionDerivationAdditional Summaries
INAP_OAC_PA_NUMBERACCUMULATIONINT8Shows the number of TCAP provider aborts during the measurement period.IACOMDPA.M197B4C1 or IACOMSPA.M197B4C1nkmtbh


Neighbour Performance Indicators

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


Neighbour.Nokia.GSM.msc_cell_cell_handovers

This section describes the counters of M337. Intra cell handover data

KPITypeData TypeDescriptionDerivationAdditional Summaries
from_neighbour_cell_nokACCUMULATIONINT8Unsuccessful handovers from adjacent cell/SAHO2NCM.M337B4C8 
from_neighbour_cell_okACCUMULATIONINT8Successful handovers from adjacent cell/SAHO2NCM.M337B4C7 
intra_cell_okACCUMULATIONINT8Number of successful intra-cell handoversHO2NCM.M337B3C5 
toneighbourcellnokACCUMULATIONINT8Unsuccessful handovers to adjacent cell/SAHO2NCM.M337B4C6 
toneighbourcellokACCUMULATIONINT8Successful handovers to adjacent cell/SAHO2NCM.M337B4C5 


Neighbour.Nokia.GSM.MSC_Handover_Neighbour_Cell

This table contains the cell specific part of the handover measurement results. Intra cell handover data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
from_neighbour_cell_nokACCUMULATIONINT8Unsuccessful handovers from adjacent cell/SAHO2NCI.M337B4C8 
from_neighbour_cell_okACCUMULATIONINT8Successful handovers from adjacent cell/SAHO2NCI.M337B4C7 
succ_intra_cell_hoACCUMULATIONINT8The number of successful intra-cell handovers.HO2NCI.M337B3C5 
succ_to_adjac_cell_hoACCUMULATIONINT8The number of successful handovers to the adjacent cell.HO2NCI.M337B4C5 
toneighbourcellnokACCUMULATIONINT8Unsuccessful handovers to adjacent cell/SAHO2NCI.M337B4C6 


Neighbour_BSC Performance Indicators

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


Neighbour_BSC.Nokia.GSM.Handover_BSC

The handover measurement shows the number of different type of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
neighbour_bsc_from_neighbour_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring BSCBS.M338B4C5 
neighbour_bsc_from_neighbour_okACCUMULATIONINT8Successful handovers from neighbouring BSCBS.M338B4C4 
neighbour_bsc_to_neighbour_nokACCUMULATIONINT8Unsuccessful handovers to neighbouring BSCBS.M338B4C3 
neighbour_bsc_to_neighbour_okACCUMULATIONINT8Successful handovers to neighbouring BSCBS.M338B4C2 


Neighbour_BSC.Nokia.GSM.Handover_Neighbour_BSC

The handover measurement shows the number of different type of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
neighbour_bsc_from_neighbour_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring BSCHMRBC1.M338B4C5 
neighbour_bsc_from_neighbour_okACCUMULATIONINT8Successful handovers from neighbouring BSCHMRBC1.M338B4C4 
neighbour_bsc_to_neighbour_nokACCUMULATIONINT8Unsuccessful handovers to neighbouring BSCHMRBC1.M338B4C3 
neighbour_bsc_to_neighbour_okACCUMULATIONINT8Successful handovers to neighbouring BSCHMRBC1.M338B4C2 
neighbour_rnc_from_neighbour_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring BSCHMRBC1.M338B5C7 
neighbour_rnc_from_neighbour_okACCUMULATIONINT8Successful handovers from neighbouring BSCHMRBC1.M338B5C6 
neighbour_rnc_to_neighbour_nokACCUMULATIONINT8Unsuccessful handovers to neighbouring BSCHMRBC1.M338B5C5 
neighbour_rnc_to_neighbour_okACCUMULATIONINT8Successful handovers to neighbouring BSCHMRBC1.M338B5C4 


Neighbour_BSC.Nokia.GSM.Handover_Neighbour_RNC

The handover measurement shows the number of different type of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
neighbour_rnc_from_neighbour_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring RNCHMRRC.M338B5C7 
neighbour_rnc_from_neighbour_okACCUMULATIONINT8Successful handovers from neighbouring RNCHMRRC.M338B5C6 
neighbour_rnc_to_neighbour_nokACCUMULATIONINT8Unsuccessful handovers to neighbouring RNCHMRRC.M338B5C5 
neighbour_rnc_to_neighbour_okACCUMULATIONINT8Successful handovers to neighbouring RNCHMRRC.M338B5C4 


Neighbour_BSC.Nokia.GSM.Handover_RNC

The handover measurement shows the number of different type of handovers.

KPITypeData TypeDescriptionDerivationAdditional Summaries
neighbour_rnc_from_neighbour_nokACCUMULATIONINT8Unsuccessful handovers from neighbouring RNCBRC.M338B5C7 
neighbour_rnc_from_neighbour_okACCUMULATIONINT8Successful handovers from neighbouring RNCBRC.M338B5C6 
neighbour_rnc_to_neighbour_nokACCUMULATIONINT8Unsuccessful handovers to neighbouring RNCBRC.M338B5C5 
neighbour_rnc_to_neighbour_okACCUMULATIONINT8Successful handovers to neighbouring RNCBRC.M338B5C4 


PIU Performance Indicators

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


PIU.Nokia.GSM.LAN_Switch_Availability

LAN Switch Availability

KPITypeData TypeDescriptionDerivationAdditional Summaries
COLD_RESTARTSACCUMULATIONINT8Shows the number of cold restarts. If value is FFFFFFFF, field is not shown.CLANSAPI.M290B2C3 or HLANSAPI.M290B2C3 or MLANSAPI.M290B2C3 
LAST_RESTART_TIMEINTENSITYINT8Shows the time of the last restart.CLANSAPI.M290B2C4 or HLANSAPI.M290B2C4 or MLANSAPI.M290B2C4 
TOPOLOGY_CHANGESACCUMULATIONINT8Shows the number of topology changes.CLANSAPI.M290B2C5 or HLANSAPI.M290B2C5 or MLANSAPI.M290B2C5 
WARM_RESTARTSACCUMULATIONINT8Shows the number of warm restarts.CLANSAPI.M290B2C2 or HLANSAPI.M290B2C2 or MLANSAPI.M290B2C2 


Processor Performance Indicators

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


Processor.Nokia.GSM.CDR_Generation

Call Data Record generation measurements

The performance data measurements for this KPI group are recorded against the combination of Processor and CDR_Type (cdr_type_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
attemptACCUMULATIONINT8This field shows the amount of cases when CDR generation was triggered. This field is not updated if the CDR type is NOT KNOWN.CDRT.M393B10C1 
failedACCUMULATIONINT8This field shows the amount of cases when the CDR generation was not successful. The NOT KNOWN CDR type row is updated when the CDR type cannot be recognised from the generation request.CDRT.M393B10C2 
successACCUMULATIONINT8This field shows the amount of CDRs successfully generated and stored to the buffer. This field is not updated if the CDR type is NOT KNOWN.CDRT.M393B10C3 


Processor.Nokia.GSM.CDRs

CDR data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
attemptACCUMULATIONINT8(Obsolete in M13.5 and KPI moved to CDR_Generation KPI Group) This field shows the amount of cases when CDR generation was triggered. This field is not updated if the CDR type is NOT KNOWN.CDR.Obsoletenkmtbh, nkpmlbh
data_missing_from_the_reportACCUMULATIONINT8This message appears in the report only if one of the counter collecting program blocks was restarted during the measurement period resulting in data loss regarding the counter values. In the XML report, this counter can appear with value 1.CDR.M393B13C1nkmtbh, nkpmlbh
failedACCUMULATIONINT8(Obsolete in M13.5 and KPI moved to CDR_Generation KPI Group) This field shows the amount of cases when the CDR generation was not successful. The NOT KNOWN CDR type row is updated when the CDR type cannot be recognised from the generation request.CDR.Obsoletenkmtbh, nkpmlbh
order_number_of_first_cdrACCUMULATIONINT8This field shows the sequence number of the first CDR in the measurement period.CDR.M393B2C1nkmtbh, nkpmlbh
order_number_of_last_cdrACCUMULATIONINT8This field shows the sequence number of the last CDR in the measurement period.CDR.M393B2C2nkmtbh, nkpmlbh
successACCUMULATIONINT8(Obsolete in M13.5 and KPI moved to CDR_Generation KPI Group) This field shows the amount of CDRs successfully generated and stored to the buffer. This field is not updated if the CDR type is NOT KNOWN.CDR.Obsoletenkmtbh, nkpmlbh
tot_nbr_cdr_loss_buf_overflowACCUMULATIONINT8This field shows the amount of CDRs lost in the buffer because of overflow.CDR.M393B1C1nkmtbh, nkpmlbh
unit_restartedACCUMULATIONINT8This field shows the sequence number of the last CDR in the measurement period.CDR.M393B12C1nkmtbh, nkpmlbh


Processor.Nokia.GSM.CDS_Availability

This section describes the restart measurement in CDS.

KPITypeData TypeDescriptionDerivationAdditional Summaries
restmeas_adm_restartsACCUMULATIONINT8Number of unit restarts initiated by the operator with MML commands (0...999999999). The field is updated immediately after a restart.RESTC.M608B2C2nkcdstbh, nkpclbh
restmeas_disk_timeACCUMULATIONINT8Time during which the unit has been out of service (0...999999999 seconds). The value is updated in a field of the unit in WO-EX state.RESTC.M608B2C5nkcdstbh, nkpclbh
restmeas_duplex_dtimeACCUMULATIONINT8In duplicated units, time during which both units have been out of service, that is, in some other state but not WO-EX or SPEX(0...999999999 seconds). The field is updated when the active unit is in WO-EXstate and only for the active unit.RESTC.M608B2C4nkcdstbh, nkpclbh
restmeas_duplex_restartsACCUMULATIONINT8Number of simultaneous restarts in duplicated units (0...999999999). The value is updated in a field of the unit that was the spare unit before the restart.RESTC.M608B2C3nkcdstbh, nkpclbh
restmeas_fam_restartsACCUMULATIONINT8Number of restarts in the program blocks of the units (0...999999999). The field is updated when the unit state administration service has restarted the program block in question.RESTC.M608B2C6nkcdstbh, nkpclbh
restmeas_invalid_recordINTENSITYINTEGERThis counter exist when unit type is 0x00 (or 0xFFFF which is fault case), in that case only this counter is printed and localmoid is DN:UNIT-UNKNOWN.RESTC.M608B2C8nkcdstbh, nkpclbh
restmeas_unit_restartsACCUMULATIONINT8Number of all unit restarts (0...999999999).The field is updated immediately after a restart.RESTC.M608B2C1nkcdstbh, nkpclbh


Processor.Nokia.GSM.CDS_CPU_Load

This section describes the unit load measurement in CDS.

KPITypeData TypeDescriptionDerivationAdditional Summaries
comp_average_loadINTENSITYFLOATThe average load rate in percentageULOAD.M592B2C1nkcdstbh, nkpclbh
comp_invalid_recordINTENSITYINTEGERTag appears with field value 1 when unit type and index are unknown.ULOAD.M592B2C6nkcdstbh, nkpclbh
comp_peak_load_dateINTENSITYINTEGERThe date of peak load. date in format ddmmyyyy (d = day, m = month, Y = year)ULOAD.M592B2C3nkcdstbh, nkpclbh
comp_peak_load_percentINTENSITYFLOATThe peak load rate in percentage (0...100).ULOAD.M592B2C2nkcdstbh, nkpclbh
comp_peak_load_timeINTENSITYINTEGERThe time of the peak load. ULOAD.M592B2C4nkcdstbh, nkpclbh


Processor.Nokia.GSM.CDS_Message_Bus_Load

This section describes the message bus load measurement in CDS.

KPITypeData TypeDescriptionDerivationAdditional Summaries
mb_invalid_recordINTENSITYINTEGERTag appears with field value 1 when unit type and index are unknown.UMBMC.M593B2C6nkcdstbh, nkpclbh
mb_load_averageINTENSITYFLOATThe average load rate of the message busUMBMC.M593B2C1nkcdstbh, nkpclbh
mb_peak_load_dateINTENSITYINTEGERThe date of peak load. date in format ddmmyyyyUMBMC.M593B2C3nkcdstbh, nkpclbh
mb_peak_load_timeINTENSITYINTEGERThe time of the peak load.UMBMC.M593B2C4nkcdstbh, nkpclbh
mb_peak_loadINTENSITYFLOATThe peak load rate in percentageUMBMC.M593B2C2nkcdstbh, nkpclbh


Processor.Nokia.GSM.HLR_Availability

This measurement contains the measurement results from the availability performance measurement, which is part of field reporting.

KPITypeData TypeDescriptionDerivationAdditional Summaries
adm_restartsACCUMULATIONINT8The number of administrative restarts of the unit.RESHLR.M129B2C3nkphlbh
dconn_time_dblACCUMULATIONINT8The disconnection time when both duplicated units are not in the WO-EX or SP-EX state.RESHLR.M129B2C7nkphlbh
dconn_timeACCUMULATIONINT8The disconnection time when the unit is not in the WO-EX or SP-EX state.RESHLR.M129B2C8nkphlbh
double_restartsACCUMULATIONINT8The number of times the duplicated units have been simultaneously restarted.RESHLR.M129B2C6nkphlbh
preproc_restartsACCUMULATIONINT8The number of the restarts of the preprocessors that are subordinate to the unit.RESHLR.M129B2C5nkphlbh
process_restartsACCUMULATIONINT8The number of restarts of the program blocks of the unit. RESHLR.M129B2C4nkphlbh
restartsACCUMULATIONINT8Number of restarts of the unit.RESHLR.M129B2C2nkphlbh


Processor.Nokia.GSM.HLR_CPU_Load

This measurement contains information about the load of the physical resources (computer unit) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
compl_invalid_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the actual record is invalid.CLOH.M119B2C5nkphlbh
compl_load_percentINTENSITYFLOATLoad degree of the processor / 10CLOH.M119B2C2 / 10nkphlbh
compl_unreliable_recordINTENSITYINTEGERTag appears at the end of the given counter group when the number of load samples is too small compared to the sampling interval and to the length of the observation period and the value of the field is 1.CLOH.M119B2C7nkphlbh
loadINTENSITYFLOATLoad degree of the processorCLOH.M119B2C2nkphlbh
peak_degreeINTENSITYFLOATPeak load degree of the processor.CLOH.M119B2C3nkphlbh
peak_timeINTENSITYINTEGERPeak load time of processor (16 characters).CLOH.M119B2C4nkphlbh


Processor.Nokia.GSM.HLR_Message_Bus_Load

This measurement contains information about the load of the physical resources (message bus) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
loadINTENSITYFLOATLoad degree of the message busMBHLR.M120B2C2nkphlbh
mbload_error_in_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the load data on the message bus is not obtained from the OMU, or the measurement resources of the message bus could not be reserved from the operating system.MBHLR.M120B2C6nkphlbh
peak_load_degreeINTENSITYFLOATPeak load degree of the message bus. MBHLR.M120B2C4nkphlbh
peak_load_timeINTENSITYINTEGERPeak load time of processor (16 characters). MBHLR.M120B2C5nkphlbh


Processor.Nokia.GSM.HLR_Rejected_Calls

This section describes the counters of M114. N.B. There is a secondary key of signal_protocol

The performance data measurements for this KPI group are recorded against the combination of Processor and Signal_Protocol (protocol_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
rej_error_foundINTENSITYINTEGERTag appears at the end of the given counter group with field value 244 if an unexpected error situation has occurred.REH.M114B2C13nkphlbh
rej_no_resp_from_lrmproINTENSITYINTEGERTag appears at the end of the given counter group with field value 242 if the signaling unit has not sent the required information for the following exchange-related counters: REJ_EXCHG_INC, REJ_EXCHG_INC_PERCENT*10, REJ_EXCHG_OUTGOING.REH.M114B2C10nkphlbh
rej_no_resp_from_signprbINTENSITYINTEGERTag appears at the end of the given counter group with field value 243 if the required information has not been received from the signalling process family that provides counters of the measured object.REH.M114B2C11nkphlbh
rej_observ_restartedINTENSITYINTEGERTag appears at the end of the given counter group with field value 16 if the signalling unit has not responded during the previous results accumulation period. Therefore, the observation has been restarted during the current results accumulation period. The counters is printed out during the following period.REH.M114B2C12nkphlbh
rej_report_inquiry_failINTENSITYINTEGERTag appears at the end of the given counter group with field value 241 if only part of the required information is received from the signalling process family that provides the counters of the measured object.REH.M114B2C9nkphlbh
rej_unit_inc_percentx10INTENSITYFLOATThe ticket service rejection percentage (0.0...100.0), that is, the proportion of incoming service requests rejected at the ticket service to the total number of service requests received at the ticket service.REH.M114B2C4nkphlbh
rej_unit_incomingACCUMULATIONINT8The number of rejected incoming service requests (0...999999999) at the ticket service.REH.M114B2C3nkphlbh
rej_unit_outgoingACCUMULATIONINT8The number of rejected service requests (0...999999999) that have exceeded the higher rejection limit of the messageREH.M114B2C5nkphlbh


Processor.Nokia.GSM.MSC_Availability

This measurement contains the measurement results from the availability performance measurement, which is part of field reporting.

KPITypeData TypeDescriptionDerivationAdditional Summaries
adm_restartsACCUMULATIONINT8The number of administrative restarts of the unit.RESMSC.M129B2C3nkmtbh, nkpmlbh
dconn_time_dblACCUMULATIONINT8The disconnection time when both duplicated units are not in the WO-EX or SP-EX state.RESMSC.M129B2C7nkmtbh, nkpmlbh
dconn_timeACCUMULATIONINT8The disconnection time when the unit is not in the WO-EX or SP-EX state.RESMSC.M129B2C8nkmtbh, nkpmlbh
double_restartsACCUMULATIONINT8The number of times the duplicated units have been simultaneously restarted.RESMSC.M129B2C6nkmtbh, nkpmlbh
preproc_restartsACCUMULATIONINT8The number of the restarts of the preprocessors that are subordinate to the unit.RESMSC.M129B2C5nkmtbh, nkpmlbh
process_restartsACCUMULATIONINT8The number of restarts of the program blocks of the unit. RESMSC.M129B2C4nkmtbh, nkpmlbh
rest_unit_restartsACCUMULATIONINT8Number of all unit restarts (0...999999999). The field is updated immediately after a restart.RESMSC.M129B2C2nkmtbh, nkpmlbh


Processor.Nokia.GSM.MSC_CPU_Load

This measurement contains information about the load of the physical resources (computer unit) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
compl_invalid_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the actual record is invalid.CLOM.M119B2C5nkmtbh, nkpmlbh
compl_unreliable_recordINTENSITYINTEGERTag appears at the end of the given counter group when the number of load samples is too small compared to the sampling interval and to the length of the observation period and the value of the field is 1.CLOM.M119B2C7nkmtbh, nkpmlbh
loadINTENSITYFLOATThe average load rateCLOM.M119B2C2nkmtbh, nkpmlbh
peak_degreeINTENSITYFLOATPeak load degree of the processor.CLOM.M119B2C3nkmtbh, nkpmlbh
peak_timeINTENSITYINTEGERPeak load time of processor (16 characters).CLOM.M119B2C4nkmtbh, nkpmlbh


Processor.Nokia.GSM.MSC_Message_Bus_Load

This measurement contains information about the load of the physical resources (message bus) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
loadINTENSITYFLOATLoad degree of the message busMBMSC.M120B2C2nkmtbh, nkpmlbh
mbload_error_in_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the load data on the message bus is not obtained from the OMU, or the measurement resources of the message bus could not be reserved from the operating system.MBMSC.M120B2C6nkmtbh, nkpmlbh
peak_load_degreeINTENSITYFLOATPeak load degree of the message bus. MBMSC.M120B2C4nkmtbh, nkpmlbh
peak_load_timeINTENSITYINTEGERPeak load time of processor (16 characters). MBMSC.M120B2C5nkmtbh, nkpmlbh


Processor.Nokia.GSM.MSC_Rejected_Calls

This section describes the counters of M114. N.B. There is a secondary key of signal_protocol

The performance data measurements for this KPI group are recorded against the combination of Processor and Signal_Protocol (TICKETSERV_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ratio_rej_callsINTENSITYFLOATThe ratio for rejected calls based on the window access controlREM.M114B2C3nkmtbh, nkpmlbh
rej_error_foundINTENSITYINTEGERTag appears at the end of the given counter group with field value 244 if an unexpected error situation has occurred.REM.M114B2C13nkmtbh, nkpmlbh
rej_no_resp_from_lrmproINTENSITYINTEGERTag appears at the end of the given counter group with field value 242 if the signaling unit has not sent the required information for the following exchange-related counters: REJ_EXCHG_INC, REJ_EXCHG_INC_PERCENT*10, REJ_EXCHG_OUTGOING.REM.M114B2C10nkmtbh, nkpmlbh
rej_no_resp_from_signprbINTENSITYINTEGERTag appears at the end of the given counter group with field value 243 if the required information has not been received from the signalling process family that provides counters of the measured object.REM.M114B2C11nkmtbh, nkpmlbh
rej_observ_restartedINTENSITYINTEGERTag appears at the end of the given counter group with field value 16 if the signalling unit has not responded during the previous results accumulation period. Therefore, the observation has been restarted during the current results accumulation period. The counters is printed out during the following period.REM.M114B2C12nkmtbh, nkpmlbh
rej_out_calls_up_limitACCUMULATIONINT8The number of outgoing calls rejected due to the upper control limit in the message buffer.REM.M114B2C5nkmtbh, nkpmlbh
rej_report_inquiry_failINTENSITYINTEGERTag appears at the end of the given counter group with field value 241 if only part of the required information is received from the signalling process family that provides the counters of the measured object.REM.M114B2C9nkmtbh, nkpmlbh
rej_unit_inc_percentx10INTENSITYFLOATThe ticket service rejection percentage (0.0...100.0), that is, the proportion of incoming service requests rejected at the ticket service to the total number of service requests received at the ticket service.REM.M114B2C4nkmtbh, nkpmlbh


Processor.Nokia.GSM.SIP_registration

SIP registration data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
auth_requestsACCUMULATIONINT8Shows the total number of sent 401 (UNAUTHORIZED) messages by MSS to SIP UA.SIP.M357B4C2nkmtbh, nkpmlbh
call_setup_att_authACCUMULATIONINT8Shows the number of authentication attempts during an invite session (first 401 UNAUTHORIZED message is sent).SIP.M357B3C17nkmtbh, nkpmlbh
call_setup_succ_authACCUMULATIONINT8Is updated if correct authentication credentials are received from SIP UA in case of invite session.SIP.M357B3C18nkmtbh, nkpmlbh
challenges_per_succ_authACCUMULATIONINT8Shows the number of sent 401 (UNAUTHORIZED) messages by MSS to SIP UA in case of successful registration (how many authentications were needed for one successful registration).SIP.M357B4C3nkmtbh, nkpmlbh
initial_reg_att_authACCUMULATIONINT8Shows the number of authentication attempts during initial registration (first 401 UNAUTHORIZED message is sent).SIP.M357B3C11nkmtbh, nkpmlbh
initial_reg_attACCUMULATIONINT8Shows the number of initial registrations (SIP initial REGISTER message is received and the subscriber data is not found in SPD database).SIP.M357B3C1nkmtbh, nkpmlbh
initial_reg_succ_authACCUMULATIONINT8Is updated if correct authentication credentials are received from SIP UA in case of initial registration.SIP.M357B3C12nkmtbh, nkpmlbh
initial_reg_succACCUMULATIONINT8Shows the number of successful initial registrations that ended with SIP 200 OK final response.SIP.M357B3C2nkmtbh, nkpmlbh
instant_message_att_authACCUMULATIONINT8Shows the number of authentication attempts during an instant message session (first 401 UNAUTHORIZED message is sent).SIP.M357B3C19nkmtbh, nkpmlbh
instant_message_succ_authACCUMULATIONINT8Is updated if correct authentication credentials are received from SIP UA in case of instant message sessionSIP.M357B3C20nkmtbh, nkpmlbh
ldap_query_attACCUMULATIONINT8Shows the number of LDAP queries when subscriber data is requested from LDAP server.SIP.M357B3C3nkmtbh, nkpmlbh
ldap_query_succACCUMULATIONINT8Is updated if the subscriber data is successfully fetched from LDAP server.SIP.M357B3C4nkmtbh, nkpmlbh
missing_dataACCUMULATIONINT8If a message (data) from the SCPU is missing, this line is printed at the report block of that SCPU. The possible value is 1, or this field does not appear in the report.SIP.M357B5C0nkmtbh, nkpmlbh
network_initiated_deregACCUMULATIONINT8When registration timer expires, MSS either deletes subscriber or initiates deregistration depending on what the operator configures. Another issue is when HLR deletes the subscriber. In both cases this counter is updated.SIP.M357B4C1nkmtbh, nkpmlbh
rereg_att_authACCUMULATIONINT8Shows the number of authentication attempts during a reregistration (first 401 UNAUTHORIZED message is sent).SIP.M357B3C13nkmtbh, nkpmlbh
rereg_attACCUMULATIONINT8Shows the number of reregistration attempts (SIP REGISTER message is received and subscriber data is found in SPD database).SIP.M357B3C7nkmtbh, nkpmlbh
rereg_succ_authACCUMULATIONINT8Is updated if correct authentication credentials are received from SIP UA in case of reregistration.SIP.M357B3C14nkmtbh, nkpmlbh
rereg_succACCUMULATIONINT8Is updated if reregistration was successful (SIP 200 OK final response is sent).SIP.M357B3C8nkmtbh, nkpmlbh
restart_in_scpuACCUMULATIONINT8Indicates that restart occurred in the specified SCPU during the measurement. The counters are unreliable. The possible value is 1, or this field does not appear in the report.SIP.M357B5C2nkmtbh, nkpmlbh
sip_reg_messageACCUMULATIONINT8Shows the total number of received SIP REGISTER messages.SIP.M357B5C1nkmtbh, nkpmlbh
user_initiated_dereg_att_authACCUMULATIONINT8Shows the number of authentication attempts during a deregistration (first 401 UNAUTHORIZED message is sent).SIP.M357B3C15nkmtbh, nkpmlbh
user_initiated_dereg_attACCUMULATIONINT8Shows the number of deregistrations made by the subscriber (MSS receives SIP REGISTER messages with zero expiry value).SIP.M357B3C9nkmtbh, nkpmlbh
user_initiated_dereg_succ_authACCUMULATIONINT8Is updated if correct authentication credentials are received from SIP UA in case of user initiated deregistration.SIP.M357B3C16nkmtbh, nkpmlbh
user_initiated_dereg_succACCUMULATIONINT8Is updated when deregistration was successful (SIP 200 OK final response is sent).SIP.M357B3C10nkmtbh, nkpmlbh


Processor.Nokia.GSM.SRR_Availability

This measurement contains the measurement results from the availability performance measurement, which is part of field reporting.

KPITypeData TypeDescriptionDerivationAdditional Summaries
rest_adm_restartsACCUMULATIONINT8The number of administrative restarts of the unit.RESSRR.M129B2C3nkpslbh, nksrrotbh
rest_disk_time_secACCUMULATIONINT8The disconnection time when the unit is not in the WO-EX or SP-EX state.RESSRR.M129B2C8nkpslbh, nksrrotbh
rest_duplex_dtime_secACCUMULATIONINT8The disconnection time when both duplicated units are not in the WO-EX or SP-EX state.RESSRR.M129B2C7nkpslbh, nksrrotbh
rest_duplex_restartsACCUMULATIONINT8The number of times the duplicated units have been simultaneously restarted.RESSRR.M129B2C6nkpslbh, nksrrotbh
rest_prb_restartsACCUMULATIONINT8The number of restarts of the program blocks of the unit.RESSRR.M129B2C4nkpslbh, nksrrotbh
rest_preproc_restartsACCUMULATIONINT8The number of the restarts of the preprocessors that are subordinate to the unit.RESSRR.M129B2C5nkpslbh, nksrrotbh
rest_unit_restartsACCUMULATIONINT8Number of restarts of the unit.RESSRR.M129B2C2nkpslbh, nksrrotbh


Processor.Nokia.GSM.SRR_CPU_Load

This measurement contains information about the load of the physical resources (computer unit) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
compl_invalid_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the actual record is invalid.CLOS.M119B2C5nkpslbh, nksrrotbh
compl_load_percent_x10INTENSITYFLOATThe average load rate in percentsCLOS.M119B2C2nkpslbh, nksrrotbh
compl_peak_load_percentINTENSITYFLOATThe peak load rate in %CLOS.M119B2C3nkpslbh, nksrrotbh
compl_peak_load_time_secINTENSITYINTEGERThe time of peak load.CLOS.M119B2C4nkpslbh, nksrrotbh
compl_unreliable_recordINTENSITYINTEGERTag appears at the end of the given counter group when the number of load samples is too small compared to the sampling interval and to the length of the observation period and the value of the field is 1.CLOS.M119B2C7nkpslbh, nksrrotbh


Processor.Nokia.GSM.SRR_Message_Bus_Load

This measurement contains information about the load of the physical resources (message bus) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
mbload_error_in_recordINTENSITYINTEGERTag appears at the end of the given counter group with field value 1 when the load data on the message bus is not obtained from the OMU, or the measurement resources of the message bus could not be reserved from the operating system.MBSRR.M120B2C6nkpslbh, nksrrotbh
mbload_load_x10INTENSITYFLOATThe average load rate of the message busMBSRR.M120B2C2nkpslbh, nksrrotbh
mbload_peak_load_time_in_secINTENSITYINTEGERThe time of peak load.MBSRR.M120B2C5nkpslbh, nksrrotbh
mbload_peak_loadINTENSITYFLOATThe peak load rate in percentsMBSRR.M120B2C4nkpslbh, nksrrotbh


Processor.Nokia.GSM.SRR_Rejected_Calls

This section describes the counters of M114. N.B. There is a secondary key of signal_protocol

The performance data measurements for this KPI group are recorded against the combination of Processor and Signal_Protocol (protocol_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
rej_error_foundINTENSITYINTEGERTag appears at the end of the given counter group with field value 244 if an unexpected error situation has occurred.RES.M114B2C13nkpslbh, nksrrotbh
rej_no_resp_from_lrmproINTENSITYINTEGERTag appears at the end of the given counter group with field value 242 if the signaling unit has not sent the required information for the following exchange-related counters: REJ_EXCHG_INC, REJ_EXCHG_INC_PERCENT*10, REJ_EXCHG_OUTGOING.RES.M114B2C10nkpslbh, nksrrotbh
rej_no_resp_from_signprbINTENSITYINTEGERTag appears at the end of the given counter group with field value 243 if the required information has not been received from the signalling process family that provides counters of the measured object.RES.M114B2C11nkpslbh, nksrrotbh
rej_observ_restartedINTENSITYINTEGERTag appears at the end of the given counter group with field value 16 if the signalling unit has not responded during the previous results accumulation period. Therefore, the observation has been restarted during the current results accumulation period. The counters is printed out during the following period.RES.M114B2C12nkpslbh, nksrrotbh
rej_report_inquiry_failINTENSITYINTEGERTag appears at the end of the given counter group with field value 241 if only part of the required information is received from the signalling process family that provides the counters of the measured object.RES.M114B2C9nkpslbh, nksrrotbh
rej_unit_inc_percentx10INTENSITYFLOATThe ticket service rejection percentage (0.0...100.0), that is, the proportion of incoming service requests rejected at the ticket service to the total number of service requests received at the ticket service.RES.M114B2C4nkpslbh, nksrrotbh
rej_unit_incomingACCUMULATIONINT8The number of rejected incoming service requests (0...999999999) at the ticket service.RES.M114B2C3nkpslbh, nksrrotbh
rej_unit_outgoingACCUMULATIONINT8The number of rejected service requests (0...999999999) that have exceeded the higher rejection limit of the messageRES.M114B2C5nkpslbh, nksrrotbh


Processor.Nokia.GSM.TCPIP_ICP6S_ICMP_messages_received

ICP6S ICMP messages received

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_icp6s_indstunreachACCUMULATIONINT8The number of received ICMP Destination Unreachable messages.TCPIP.M563B7C27nkmtbh, nkpmlbh
tcpip_icp6s_inechoreplyACCUMULATIONINT8The number of received ICMP Echo Replymessages.TCPIP.M563B7C32nkmtbh, nkpmlbh
tcpip_icp6s_inechoACCUMULATIONINT8The number of received ICMP Echo Request messages.TCPIP.M563B7C31nkmtbh, nkpmlbh
tcpip_icp6s_inmlddoneACCUMULATIONINT8The number of received ICMP MulticastListener Done messages.TCPIP.M563B7C35nkmtbh, nkpmlbh
tcpip_icp6s_inmldqueryACCUMULATIONINT8The number of received ICMP MulticastListener Query messages.TCPIP.M563B7C33nkmtbh, nkpmlbh
tcpip_icp6s_inmldreportACCUMULATIONINT8The number of received ICMP MulticastListener Report messages.TCPIP.M563B7C34nkmtbh, nkpmlbh
tcpip_icp6s_inneighboradvertACCUMULATIONINT8The number of received ICMP NeighbourAdvertisement messages.TCPIP.M563B7C39nkmtbh, nkpmlbh
tcpip_icp6s_inneighborsolicitACCUMULATIONINT8The number of received ICMP NeighbourSolicitation messages.TCPIP.M563B7C38nkmtbh, nkpmlbh
tcpip_icp6s_inniqueryACCUMULATIONINT8The number of received ICMP NodeInformation Query messages.TCPIP.M563B7C42nkmtbh, nkpmlbh
tcpip_icp6s_innireplyACCUMULATIONINT8The number of received ICMP NodeInformation Reply messages.TCPIP.M563B7C43nkmtbh, nkpmlbh
tcpip_icp6s_inparamprobACCUMULATIONINT8The number of received ICMP Parameter Problem messages.TCPIP.M563B7C30nkmtbh, nkpmlbh
tcpip_icp6s_inpkttoobigACCUMULATIONINT8The number of received ICMP Packet Too Big messages.TCPIP.M563B7C28nkmtbh, nkpmlbh
tcpip_icp6s_inredirectACCUMULATIONINT8The number of received ICMP Redirectmessages.TCPIP.M563B7C40nkmtbh, nkpmlbh
tcpip_icp6s_inrouteradvertACCUMULATIONINT8The number of received ICMP RouterAdvertisement messages.TCPIP.M563B7C37nkmtbh, nkpmlbh
tcpip_icp6s_inrouterrenumberACCUMULATIONINT8The number of received ICMPv6 RouterRenumbering messages.TCPIP.M563B7C41nkmtbh, nkpmlbh
tcpip_icp6s_inroutersolicitACCUMULATIONINT8The number of received ICMP RouterSolicitation messages.TCPIP.M563B7C36nkmtbh, nkpmlbh
tcpip_icp6s_intimeexceedACCUMULATIONINT8The number of received ICMP Time Exceeded messages.TCPIP.M563B7C29nkmtbh, nkpmlbh
tcpip_icps_inechoreplyACCUMULATIONINT8The number of received ICMP Echo Reply messages.TCPIP.M563B3C4nkmtbh, nkpmlbh
tcpip_icps_inechoACCUMULATIONINT8The number of received ICMP Echo (request) messages.TCPIP.M563B3C8nkmtbh, nkpmlbh
tcpip_icps_inireqACCUMULATIONINT8Number of received ICMP InformationRequest messages.TCPIP.M563B3C15nkmtbh, nkpmlbh
tcpip_icps_inireqreplyACCUMULATIONINT8Number of received ICMP Information Replymessages.TCPIP.M563B3C16nkmtbh, nkpmlbh
tcpip_icps_inmaskreplyACCUMULATIONINT8The number of received ICMP Address MaskReply messages.TCPIP.M563B3C18nkmtbh, nkpmlbh
tcpip_icps_inmaskreqACCUMULATIONINT8The number of received ICMP Address MaskRequest messages.TCPIP.M563B3C17nkmtbh, nkpmlbh
tcpip_icps_inparamprobACCUMULATIONINT8The number of received ICMP Parameter Problem messages.TCPIP.M563B3C12nkmtbh, nkpmlbh
tcpip_icps_inredirectACCUMULATIONINT8The number of received ICMP Redirect messages.TCPIP.M563B3C7nkmtbh, nkpmlbh
tcpip_icps_inrouteradvertACCUMULATIONINT8Number of received ICMP Router Advertisement messages.TCPIP.M563B3C9nkmtbh, nkpmlbh
tcpip_icps_inroutersolicitACCUMULATIONINT8Number of received ICMP Router Solicitation messages.TCPIP.M563B3C10nkmtbh, nkpmlbh
tcpip_icps_insourcequenchACCUMULATIONINT8Number of received ICMP Source Quench messages.TCPIP.M563B3C6nkmtbh, nkpmlbh
tcpip_icps_intimxceedACCUMULATIONINT8The number of received ICMP Time Exceeded messages.TCPIP.M563B3C11nkmtbh, nkpmlbh
tcpip_icps_intstampreplyACCUMULATIONINT8The number of received ICMP TimestampReply messages.TCPIP.M563B3C14nkmtbh, nkpmlbh
tcpip_icps_intstampACCUMULATIONINT8The number of received ICMP Time stamp(request) messages.TCPIP.M563B3C13nkmtbh, nkpmlbh
tcpip_icps_inunreachACCUMULATIONINT8Number of received ICMP Destination Unreachable messages.TCPIP.M563B3C5nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_ICP6S_ICMP_messages_sent

ICP6S ICMP messages sent

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_icp6s_outdstunreachACCUMULATIONINT8The number of ICMP Destination Unreachable messages sent.TCPIP.M563B7C5nkmtbh, nkpmlbh
tcpip_icp6s_outechoreplyACCUMULATIONINT8The number of ICMP Echo Reply messages sent.TCPIP.M563B7C10nkmtbh, nkpmlbh
tcpip_icp6s_outechoACCUMULATIONINT8The number of ICMP Echo Request messages sent.TCPIP.M563B7C9nkmtbh, nkpmlbh
tcpip_icp6s_outmlddoneACCUMULATIONINT8The number of ICMP Multicast Listener Donemessages sent.TCPIP.M563B7C13nkmtbh, nkpmlbh
tcpip_icp6s_outmldqueryACCUMULATIONINT8The number of ICMP Multicast Listener Querymessages sent.TCPIP.M563B7C11nkmtbh, nkpmlbh
tcpip_icp6s_outmldreportACCUMULATIONINT8The number of ICMP Multicast ListenerReport messages sent.TCPIP.M563B7C12nkmtbh, nkpmlbh
tcpip_icp6s_outneighboradvertACCUMULATIONINT8The number of ICMP NeighbourAdvertisement messages sent.TCPIP.M563B7C17nkmtbh, nkpmlbh
tcpip_icp6s_outneighborsolicitACCUMULATIONINT8The number of ICMP Neighbour Solicitation messages sent.TCPIP.M563B7C16nkmtbh, nkpmlbh
tcpip_icp6s_outniqueryACCUMULATIONINT8The number of ICMP Node Information Querymessages sent.TCPIP.M563B7C20nkmtbh, nkpmlbh
tcpip_icp6s_outnireplyACCUMULATIONINT8The number of ICMP Node Information Reply messages sent.TCPIP.M563B7C21nkmtbh, nkpmlbh
tcpip_icp6s_outparamprobACCUMULATIONINT8The number of ICMP Parameter problem messages sent.TCPIP.M563B7C8nkmtbh, nkpmlbh
tcpip_icp6s_outpkttoobigACCUMULATIONINT8The number of ICMP Packet Too Big messages sent.TCPIP.M563B7C6nkmtbh, nkpmlbh
tcpip_icp6s_outredirectACCUMULATIONINT8The number of ICMP Redirect messagesent. For a host, this object will always bezero, since hosts do not send redirects.TCPIP.M563B7C18nkmtbh, nkpmlbh
tcpip_icp6s_outrouteradvertACCUMULATIONINT8The number of ICMP Router Advertisement messages sent.TCPIP.M563B7C15nkmtbh, nkpmlbh
tcpip_icp6s_outrouterrenumberACCUMULATIONINT8The number of ICMP Router Renumberingmessages sent.TCPIP.M563B7C19nkmtbh, nkpmlbh
tcpip_icp6s_outroutersolicitACCUMULATIONINT8The number of ICMP Router Solicitation messages sent.TCPIP.M563B7C14nkmtbh, nkpmlbh
tcpip_icp6s_outtimeexceedACCUMULATIONINT8The number of ICMP Time Exceeded messages sent.TCPIP.M563B7C7nkmtbh, nkpmlbh
tcpip_icps_outechoACCUMULATIONINT8The number of ICMP Echo (request)messages sent.TCPIP.M563B3C27nkmtbh, nkpmlbh
tcpip_icps_outireqACCUMULATIONINT8Number of ICMP Information Request messages sent.TCPIP.M563B3C34nkmtbh, nkpmlbh
tcpip_icps_outireqreplyACCUMULATIONINT8Number of ICMP Information Reply messages sent.TCPIP.M563B3C35nkmtbh, nkpmlbh
tcpip_icps_outmaskreplyACCUMULATIONINT8The number of ICMP Address Mask Replymessages sent.TCPIP.M563B3C37nkmtbh, nkpmlbh
tcpip_icps_outmaskreqACCUMULATIONINT8The number of ICMP Address Mask Request messages sent.TCPIP.M563B3C36nkmtbh, nkpmlbh
tcpip_icps_outparamprobACCUMULATIONINT8The number of ICMP Parameter Problem messages sent.TCPIP.M563B3C31nkmtbh, nkpmlbh
tcpip_icps_outredirectACCUMULATIONINT8The number of ICMP Redirect message sent. For a host, this object will always bezero, since hosts do not send redirects.TCPIP.M563B3C26nkmtbh, nkpmlbh
tcpip_icps_outsourcequenchACCUMULATIONINT8The number of ICMP Source Quenchmessages sent.TCPIP.M563B3C25nkmtbh, nkpmlbh
tcpip_icps_outtimxceedACCUMULATIONINT8The number of ICMP Time Exceeded messages sent.TCPIP.M563B3C30nkmtbh, nkpmlbh
tcpip_icps_outtstampreplyACCUMULATIONINT8The number of ICMP Timestamp Reply messages sent.TCPIP.M563B3C33nkmtbh, nkpmlbh
tcpip_icps_outtstampACCUMULATIONINT8The number of ICMP Timestamp (request )messages sent.TCPIP.M563B3C32nkmtbh, nkpmlbh
tcpip_icps_outunreachACCUMULATIONINT8The number of ICMP DestinationUnreachable messages sent.TCPIP.M563B3C24nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_ICP6S_ICMP

TCPIP ICP6S ICMP messages

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_icp6s_badcodeACCUMULATIONINT8The number of ICMP messages with aninvalid code.TCPIP.M563B7C22nkmtbh, nkpmlbh
tcpip_icp6s_badlenACCUMULATIONINT8The number of ICMP messages with aninvalid ICMPv6 body.TCPIP.M563B7C25nkmtbh, nkpmlbh
tcpip_icp6s_canterrorACCUMULATIONINT8Number of times when errors were not generated because the old packet protocol was ICMPv6 error message.TCPIP.M563B7C3nkmtbh, nkpmlbh
tcpip_icp6s_checksumACCUMULATIONINT8The number of ICMP messages with aninvalid ICMPv6 checksum.TCPIP.M563B7C24nkmtbh, nkpmlbh
tcpip_icp6s_dstunreachaddrACCUMULATIONINT8The number of ICMPv6 DestinationUnreachable messages with address unreachable (3) code.TCPIP.M563B7C47nkmtbh, nkpmlbh
tcpip_icp6s_dstunreachadminACCUMULATIONINT8The number of ICMPv6 Destination Unreachable messages with communicationwith destination administratively prohibited (1)code.TCPIP.M563B7C45nkmtbh, nkpmlbh
tcpip_icp6s_dstunreachbeyondscACCUMULATIONINT8The number of ICMPv6 DestinationUnreachable messages with beyond scope(2) code.TCPIP.M563B7C46nkmtbh, nkpmlbh
tcpip_icp6s_dstunreachnoportACCUMULATIONINT8The number of ICMPv6 Destination Unreachable messages with port unreachable(4) code.TCPIP.M563B7C48nkmtbh, nkpmlbh
tcpip_icp6s_dstunreachnorouteACCUMULATIONINT8The number of ICMPv6 Destination Unreachable messages with no route to destination (0) code.TCPIP.M563B7C44nkmtbh, nkpmlbh
tcpip_icp6s_errorACCUMULATIONINT8The number of ICMP messages having ICMP specificerrors, such as ICMP checksum, badlength, lack of buffer, and so on.TCPIP.M563B7C2nkmtbh, nkpmlbh
tcpip_icp6s_nd_toomanyoptACCUMULATIONINT8The number of ICMPv6 messages with too many ND options.TCPIP.M563B7C57nkmtbh, nkpmlbh
tcpip_icp6s_packettoobigACCUMULATIONINT8The number of ICMPv6 Packet Too Bigmessages (with code 0).TCPIP.M563B7C49nkmtbh, nkpmlbh
tcpip_icp6s_paramprobheaderACCUMULATIONINT8The number of ICMPv6 Parameter Problem messages with erroneous header fieldencountered (0) code.TCPIP.M563B7C52nkmtbh, nkpmlbh
tcpip_icp6s_paramprobnextheaACCUMULATIONINT8The number of ICMPv6 Parameter Problemmessages with unrecognized Next Headertype encountered (1) codeTCPIP.M563B7C53nkmtbh, nkpmlbh
tcpip_icp6s_paramproboptionACCUMULATIONINT8The number of ICMPv6 Parameter Problemmessages with unrecognized IPv6 optionencountered (2) code.TCPIP.M563B7C54nkmtbh, nkpmlbh
tcpip_icp6s_redirectACCUMULATIONINT8The number of ICMPv6 Redirect messages.TCPIP.M563B7C55nkmtbh, nkpmlbh
tcpip_icp6s_reflectACCUMULATIONINT8The number of generated ICMPv6 message responses.TCPIP.M563B7C26nkmtbh, nkpmlbh
tcpip_icp6s_timeexceedreassembACCUMULATIONINT8The number of ICMPv6 Time Exceeded messages with fragment reassembly timeexceeded (1) code.TCPIP.M563B7C51nkmtbh, nkpmlbh
tcpip_icp6s_timeexceedtransitACCUMULATIONINT8The number of ICMPv6 Time Exceededmessages with hop limit exceeded in transit(0) code.TCPIP.M563B7C50nkmtbh, nkpmlbh
tcpip_icp6s_toofregACCUMULATIONINT8Number of times when errors were not generated because of rate limitation.TCPIP.M563B7C4nkmtbh, nkpmlbh
tcpip_icp6s_tooshortACCUMULATIONINT8The number of ICMP messages with anICMPv6 header shorter than the minimumlength.TCPIP.M563B7C23nkmtbh, nkpmlbh
tcpip_icp6s_unknownACCUMULATIONINT8The number of unknown ICMP messages.TCPIP.M563B7C56nkmtbh, nkpmlbh
tcpip_icps_badcodeACCUMULATIONINT8Number of ICMP messages that have badcode fields.TCPIP.M563B3C19nkmtbh, nkpmlbh
tcpip_icps_badlenACCUMULATIONINT8The number of ICMP messages with invalidICMP body.TCPIP.M563B3C22nkmtbh, nkpmlbh
tcpip_icps_checksumACCUMULATIONINT8The number of ICMP messages with invalidICMP checksum.TCPIP.M563B3C21nkmtbh, nkpmlbh
tcpip_icps_errorACCUMULATIONINT8The number of ICMP messages having ICMP specific errors such as ICMP checksum, badlength, lack of buffer and so on.TCPIP.M563B3C2nkmtbh, nkpmlbh
tcpip_icps_oldicmpACCUMULATIONINT8Number of times when errors are not generated because the old packet protocol was ICMP error message.TCPIP.M563B3C3nkmtbh, nkpmlbh
tcpip_icps_outechoreplyACCUMULATIONINT8The number of ICMP Echo Reply messagesent.TCPIP.M563B3C23nkmtbh, nkpmlbh
tcpip_icps_outrouteradvertACCUMULATIONINT8Number of ICMP Router Advertisement messages.TCPIP.M563B3C28nkmtbh, nkpmlbh
tcpip_icps_outroutersolicitACCUMULATIONINT8Number of ICMP Router Solicitation messages.TCPIP.M563B3C29nkmtbh, nkpmlbh
tcpip_icps_reflectACCUMULATIONINT8The number of generated ICMP message responses.TCPIP.M563B3C38nkmtbh, nkpmlbh
tcpip_icps_tooshortACCUMULATIONINT8Number of ICMP messages with an ICMPheader shorter than the minimum length.TCPIP.M563B3C20nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S_depreciate_address_chosen

TCP IP version 6 depreciated address data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_source_deprecate_10ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C108nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_11ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C109nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_12ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C110nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_13ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C111nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_14ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C112nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_15ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C113nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_16ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C114nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_1ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C99nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_2ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C100nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_3ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C101nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_4ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C102nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_5ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C103nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_6ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C104nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_7ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C105nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_8ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C106nkmtbh, nkpmlbh
tcpip_ip6s_source_deprecate_9ACCUMULATIONINT8Number of times that a deprecated address is chosen.TCPIP.M563B6C107nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S_other_IF

TCP IP version 6 other interface data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_sources_otherif_10ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C60nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_11ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C61nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_12ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C62nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_13ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C63nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_14ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C64nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_15ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C65nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_16ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C66nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_1ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C51nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_2ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C52nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_3ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C53nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_4ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C54nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_5ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C55nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_6ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C56nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_7ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C57nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_8ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C58nkmtbh, nkpmlbh
tcpip_ip6s_sources_otherif_9ACCUMULATIONINT8Number of times that an address on a on outgoing I/F is chosen.TCPIP.M563B6C59nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S_other_scope

TCP IP version 6 other scope data.

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_source_otherscop_10ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C92nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_11ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C93nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_12ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C94nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_13ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C95nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_14ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C96nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_15ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C97nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_16ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C98nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_1ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C83nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_2ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C84nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_3ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C85nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_4ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C86nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_5ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C87nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_6ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C88nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_7ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C89nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_8ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C90nkmtbh, nkpmlbh
tcpip_ip6s_source_otherscop_9ACCUMULATIONINT8Number of times that an address that has a different scope from the destination is chosen.TCPIP.M563B6C91nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S_same_IF

TCP IP version 6 outgoing interface data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_sources_sameif_10ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C44nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_11ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C45nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_12ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C46nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_13ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C47nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_14ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C48nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_15ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C49nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_16ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C50nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_1ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C35nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_2ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C36nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_3ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C37nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_4ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C38nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_5ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C39nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_6ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C40nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_7ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C41nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_8ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C42nkmtbh, nkpmlbh
tcpip_ip6s_sources_sameif_9ACCUMULATIONINT8Number of times that an address on the outgoing I/F is chosen.TCPIP.M563B6C43nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S_same_scope

TCP IP version 6 destination scope data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_source_samescope_10ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C76nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_11ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C77nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_12ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C78nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_13ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C79nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_14ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C80nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_15ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C81nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_16ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C82nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_1ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C67nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_2ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C68nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_3ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C69nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_4ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C70nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_5ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C71nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_6ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C72nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_7ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C73nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_8ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C74nkmtbh, nkpmlbh
tcpip_ip6s_source_samescope_9ACCUMULATIONINT8Number of times that an address that has the same scope from the destination is chosen.TCPIP.M563B6C75nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S_sources_rule

TCP IP version 6 source selection application data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_sources_rule_10ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C124nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_11ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C125nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_12ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C126nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_13ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C127nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_14ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C128nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_15ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C129nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_16ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C130nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_1ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C115nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_2ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C116nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_3ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C117nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_4ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C118nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_5ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C119nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_6ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C120nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_7ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C121nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_8ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C122nkmtbh, nkpmlbh
tcpip_ip6s_sources_rule_9ACCUMULATIONINT8Number of times that each rule of source selection is applied.TCPIP.M563B6C123nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IP6S

TCP IP version 6 datagram and fragment data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ip6s_badoptionsACCUMULATIONINT8The number of input IPv6 datagrams discarded due to errors discovered inprocessing their IPv6 options.TCPIP.M563B6C5nkmtbh, nkpmlbh
tcpip_ip6s_badscopeACCUMULATIONINT8The number of IPv6 packets that violated scope rules.TCPIP.M563B6C23nkmtbh, nkpmlbh
tcpip_ip6s_badversACCUMULATIONINT8The number of input datagrams discarded due to version number mismatch in their IPv6headers.TCPIP.M563B6C6nkmtbh, nkpmlbh
tcpip_ip6s_cantforwardACCUMULATIONINT8The number of input datagrams discarded because the IP address in their IPv6 headerdestination field was not a valid address to beforwarded.TCPIP.M563B6C14nkmtbh, nkpmlbh
tcpip_ip6s_cantfragACCUMULATIONINT8The number of IPv6 datagrams that havebeen discarded because they needed to befragmented at this entity but could not be.TCPIP.M563B6C22nkmtbh, nkpmlbh
tcpip_ip6s_deliveredACCUMULATIONINT8The total number of datagrams successfullydelivered to IPv6 user-protocols (includingICMP). This counter is incremented at theinterface to which these datagrams wereaddressed, which is not necessarily the inputinterface for some of the datagrams.TCPIP.M563B6C12nkmtbh, nkpmlbh
tcpip_ip6s_extthdrtoolongACCUMULATIONINT8The number of IPv6 packets whose headers are not continuous.TCPIP.M563B6C29nkmtbh, nkpmlbh
tcpip_ip6s_forward_cachehitACCUMULATIONINT8The number of IPv6 packets founded route from route table.TCPIP.M563B6C32nkmtbh, nkpmlbh
tcpip_ip6s_forward_cachemissACCUMULATIONINT8The number of IPv6 packets not founded route from route table.TCPIP.M563B6C33nkmtbh, nkpmlbh
tcpip_ip6s_forwardACCUMULATIONINT8The number of output datagrams which this entity received and forwarded to their final destinations. In entities which do not act asIPv6 routers, this counter will include onlythose packets which were Source-Routed via this entity, and the Source-Route prTCPIP.M563B6C13nkmtbh, nkpmlbh
tcpip_ip6s_fragdroppedACCUMULATIONINT8The number of discarded IP fragments due to duplicates or out of space.TCPIP.M563B6C8nkmtbh, nkpmlbh
tcpip_ip6s_fragmentedACCUMULATIONINT8The number of outgoing IPv6 datagrams thathave been successfully fragmented at this entity.TCPIP.M563B6C20nkmtbh, nkpmlbh
tcpip_ip6s_fragmentsACCUMULATIONINT8The number of received IPv6 fragments.TCPIP.M563B6C7nkmtbh, nkpmlbh
tcpip_ip6s_fragoverflowACCUMULATIONINT8The number of IPv6 fragments that exceeded the limit.TCPIP.M563B6C10nkmtbh, nkpmlbh
tcpip_ip6s_fragtimeoutACCUMULATIONINT8The number of IPv6 fragments dropped aftertime out.TCPIP.M563B6C9nkmtbh, nkpmlbh
tcpip_ip6s_localoutACCUMULATIONINT8The total number of IPv6 datagrams generated at the system, not forwarded.TCPIP.M563B6C16nkmtbh, nkpmlbh
tcpip_ip6s_m1ACCUMULATIONINT8Number of times that one memory buffer has been used by the networking protocols.TCPIP.M563B6C25nkmtbh, nkpmlbh
tcpip_ip6s_m2mACCUMULATIONINT8Number of times that two or more memory buffers have been used by the networkingprotocols.TCPIP.M563B6C26nkmtbh, nkpmlbh
tcpip_ip6s_mext1ACCUMULATIONINT8Number of times that one external memory buffer has been used by the networkingprotocols.TCPIP.M563B6C27nkmtbh, nkpmlbh
tcpip_ip6s_mext2mACCUMULATIONINT8Number of times that two or more external memory buffers have been used by the networking protocols.TCPIP.M563B6C28nkmtbh, nkpmlbh
tcpip_ip6s_nogifACCUMULATIONINT8The number of tunneling IPv6 packets that can not find gif.TCPIP.M563B6C30nkmtbh, nkpmlbh
tcpip_ip6s_norouteACCUMULATIONINT8The number of input datagrams discardedbecause no route could be found to transmit them to their destination.TCPIP.M563B6C19nkmtbh, nkpmlbh
tcpip_ip6s_notmemberACCUMULATIONINT8The number of multicast IPv6 packets which do not join.TCPIP.M563B6C24nkmtbh, nkpmlbh
tcpip_ip6s_odroppedACCUMULATIONINT8The number of output IPv6 datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (for example, due to lack of buffer space).TCPIP.M563B6C18nkmtbh, nkpmlbh
tcpip_ip6s_ofragmentsACCUMULATIONINT8The number of outgoing IPv6 datagram fragments that have been generated as aresult of fragmentation at this entity.TCPIP.M563B6C21nkmtbh, nkpmlbh
tcpip_ip6s_rawoutACCUMULATIONINT8The total number of IPv6 packets generated.The number of packets sent with fabricated IPv6 header.TCPIP.M563B6C17nkmtbh, nkpmlbh
tcpip_ip6s_reassembledACCUMULATIONINT8The number of IPv6 datagrams successfully re-assembled.TCPIP.M563B6C11nkmtbh, nkpmlbh
tcpip_ip6s_redirectsentACCUMULATIONINT8The number of redirect messages sent.TCPIP.M563B6C15nkmtbh, nkpmlbh
tcpip_ip6s_sources_noneACCUMULATIONINT8Number of times that address selection fails.TCPIP.M563B6C34nkmtbh, nkpmlbh
tcpip_ip6s_toomanyhdrACCUMULATIONINT8The number of IPv6 packets discarded due to too many headers.TCPIP.M563B6C31nkmtbh, nkpmlbh
tcpip_ip6s_tooshortACCUMULATIONINT8The number of discarded IPv6 datagrams withinvalid data length.TCPIP.M563B6C3nkmtbh, nkpmlbh
tcpip_ip6s_toosmallACCUMULATIONINT8The number of discarded IPv6 datagrams dueto too small to contain IP packet.TCPIP.M563B6C4nkmtbh, nkpmlbh
tcpip_ip6s_totalACCUMULATIONINT8The total number of input datagrams received by the interface, including those received in error.TCPIP.M563B6C2nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_IPS

TCP IP fragment and datagram data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_ips_badaddrACCUMULATIONINT8The number of discarded IP datagrams which have failures of source address selection.TCPIP.M563B2C31nkmtbh, nkpmlbh
tcpip_ips_badfragsACCUMULATIONINT8The number of malformed IP fragmentsdropped.TCPIP.M563B2C15nkmtbh, nkpmlbh
tcpip_ips_badhlenACCUMULATIONINT8The number of input IP datagrams discarded due to invalid header length.TCPIP.M563B2C7nkmtbh, nkpmlbh
tcpip_ips_badlenACCUMULATIONINT8The number of input IP datagrams discarded due to inconsistent IP header and IP datalength.TCPIP.M563B2C8nkmtbh, nkpmlbh
tcpip_ips_badoptionsACCUMULATIONINT8The number of input IP datagrams discarded due to errors discovered in processing their header IP options.TCPIP.M563B2C9nkmtbh, nkpmlbh
tcpip_ips_badsumACCUMULATIONINT8The number of input IP datagrams discarded due to errors in their checksums.TCPIP.M563B2C3nkmtbh, nkpmlbh
tcpip_ips_badversACCUMULATIONINT8The number of input IP datagrams discarded due to version number mismatch.TCPIP.M563B2C10nkmtbh, nkpmlbh
tcpip_ips_cantforwardACCUMULATIONINT8The number of input datagrams discarded because the IP address in their IP header destination field was not a valid address to beforwarded.TCPIP.M563B2C20nkmtbh, nkpmlbh
tcpip_ips_cantfragACCUMULATIONINT8The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be.TCPIP.M563B2C29nkmtbh, nkpmlbh
tcpip_ips_deliveredACCUMULATIONINT8The total number of input IP datagrams successfully delivered.TCPIP.M563B2C17nkmtbh, nkpmlbh
tcpip_ips_fastforwardACCUMULATIONINT8The number of fast-forwarded IP packets.TCPIP.M563B2C28nkmtbh, nkpmlbh
tcpip_ips_forwardACCUMULATIONINT8The number of input IP datagrams for which this entity was not their final IP destination, asa result of which an attempt was made to finda route to forward them to that finaldestination.TCPIP.M563B2C19nkmtbh, nkpmlbh
tcpip_ips_fragdroppedACCUMULATIONINT8The number of discarded IP fragments due toduplicates or out of space.TCPIP.M563B2C12nkmtbh, nkpmlbh
tcpip_ips_fragmentedACCUMULATIONINT8The number of outgoing IP datagrams that have been successfully fragmented at this entity.TCPIP.M563B2C26nkmtbh, nkpmlbh
tcpip_ips_fragmentsACCUMULATIONINT8The number of received IP fragments.TCPIP.M563B2C11nkmtbh, nkpmlbh
tcpip_ips_fragtimeoutACCUMULATIONINT8The number of IP fragments dropped aftertime out.TCPIP.M563B2C13nkmtbh, nkpmlbh
tcpip_ips_localoutACCUMULATIONINT8The total number of IP datagrams generated at the system, not forwarded.TCPIP.M563B2C22nkmtbh, nkpmlbh
tcpip_ips_nogifACCUMULATIONINT8The number of tunneling IP packets that cannot find match gif.TCPIP.M563B2C30nkmtbh, nkpmlbh
tcpip_ips_noprotoACCUMULATIONINT8The number of locally-addressed datagrams received successfully but discarded because of an unknown or not supported protocol.TCPIP.M563B2C18nkmtbh, nkpmlbh
tcpip_ips_norouteACCUMULATIONINT8The number of IP datagrams discarded because no route could be found to transmit them to their destination.TCPIP.M563B2C25nkmtbh, nkpmlbh
tcpip_ips_odroppedACCUMULATIONINT8The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded for resource shortages, for example lack of buffer space.TCPIP.M563B2C24nkmtbh, nkpmlbh
tcpip_ips_ofragmentsACCUMULATIONINT8The number of outgoing IP datagram fragments that have been generated as a result of fragmentation at this entity.TCPIP.M563B2C27nkmtbh, nkpmlbh
tcpip_ips_rawoutACCUMULATIONINT8The total number of IP packets generated.The number of packets sent with fabricated IPheader.TCPIP.M563B2C23nkmtbh, nkpmlbh
tcpip_ips_rcvmemdropACCUMULATIONINT8The number of IP fragments dropped due tolack of memoryTCPIP.M563B2C14nkmtbh, nkpmlbh
tcpip_ips_reassembledACCUMULATIONINT8The number of IP datagrams successfully reassembled.TCPIP.M563B2C16nkmtbh, nkpmlbh
tcpip_ips_redirectsentACCUMULATIONINT8The number of sent redirect messages.TCPIP.M563B2C21nkmtbh, nkpmlbh
tcpip_ips_toolongACCUMULATIONINT8The number of discarded IP datagrams whose length is longer than the maximum IPpacket size.TCPIP.M563B2C6nkmtbh, nkpmlbh
tcpip_ips_tooshortACCUMULATIONINT8The number of discarded IP datagrams with invalid data length.TCPIP.M563B2C5nkmtbh, nkpmlbh
tcpip_ips_toosmallACCUMULATIONINT8The number of discarded IP datagrams due to too small to contain IP packet.TCPIP.M563B2C4nkmtbh, nkpmlbh
tcpip_ips_totalACCUMULATIONINT8The total number of input IP data grams received from interfaces, including those received in error.TCPIP.M563B2C2nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_TCPS_congestion_windows

TCP IP congestion window data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_tcps_cwr_ecnACCUMULATIONINT8The number of Congestion Windows reducedby Explicit Congestion Notification.TCPIP.M563B4C73nkmtbh, nkpmlbh
tcpip_tcps_cwr_frecoveryACCUMULATIONINT8The number of Congestion Windows reducedby fast recovery.TCPIP.M563B4C74nkmtbh, nkpmlbh
tcpip_tcps_cwr_timeoutACCUMULATIONINT8The number of Congestion Windows reducedby timeout.TCPIP.M563B4C75nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_TCPS_ECN

TCP IP explicit congestion notification data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_tcps_ecn_acceptsACCUMULATIONINT8The number of accepted Explicit Congestion Notification connections.TCPIP.M563B4C66nkmtbh, nkpmlbh
tcpip_tcps_ecn_rcvceACCUMULATIONINT8The number of received CongestionExperienced in IP header.TCPIP.M563B4C69nkmtbh, nkpmlbh
tcpip_tcps_ecn_rcvcwrACCUMULATIONINT8The number of received Congestion Window Reduces.TCPIP.M563B4C68nkmtbh, nkpmlbh
tcpip_tcps_ecn_rcveceACCUMULATIONINT8The number of received ECN-Echos.TCPIP.M563B4C67nkmtbh, nkpmlbh
tcpip_tcps_ecn_sndcwrACCUMULATIONINT8The number of Congestion Window Reduces sent.TCPIP.M563B4C72nkmtbh, nkpmlbh
tcpip_tcps_ecn_sndeceACCUMULATIONINT8The number of ECN-Echos sent.TCPIP.M563B4C71nkmtbh, nkpmlbh
tcpip_tcps_ecn_sndectACCUMULATIONINT8The number of Congestion Window Reduces sent.TCPIP.M563B4C70nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_TCPS_SYN_cache

TCP IP synchronise sequence number cache data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_tcps_sc_abortedACCUMULATIONINT8The number of TCP packet synchronize sequence numbers (SYN) cache aborted due to no space to build protocol control block(PCB).TCPIP.M563B4C57nkmtbh, nkpmlbh
tcpip_tcps_sc_addedACCUMULATIONINT8The number of added TCP packet SYN cache entries.TCPIP.M563B4C54nkmtbh, nkpmlbh
tcpip_tcps_sc_buckeoverflowACCUMULATIONINT8The number of dropped TCP packet SYN cache due to bucket overflow.TCPIP.M563B4C60nkmtbh, nkpmlbh
tcpip_tcps_sc_collisionsACCUMULATIONINT8The number of TCP packet SYN cache hash collisions.TCPIP.M563B4C55nkmtbh, nkpmlbh
tcpip_tcps_sc_completedACCUMULATIONINT8The number of TCP packet SYN cache completed.TCPIP.M563B4C56nkmtbh, nkpmlbh
tcpip_tcps_sc_droppedACCUMULATIONINT8The number of dropped TCP packet SYNs due to no route or no space.TCPIP.M563B4C64nkmtbh, nkpmlbh
tcpip_tcps_sc_dupesynACCUMULATIONINT8The number of received Duplicate TCP packet SYNs for entries already in the cache.TCPIP.M563B4C63nkmtbh, nkpmlbh
tcpip_tcps_sc_overflowedACCUMULATIONINT8The number of dropped TCP packet SYN cache due to overflow.TCPIP.M563B4C59nkmtbh, nkpmlbh
tcpip_tcps_sc_resetACCUMULATIONINT8The number of dropped TCP packet SYN cache due to RST.TCPIP.M563B4C61nkmtbh, nkpmlbh
tcpip_tcps_sc_retransmittedACCUMULATIONINT8The number of re-transmitted TCP packet SYNs and ACKs (acknowledgements).TCPIP.M563B4C65nkmtbh, nkpmlbh
tcpip_tcps_sc_timed_outACCUMULATIONINT8The number of TCP packet SYN cache timedout.TCPIP.M563B4C58nkmtbh, nkpmlbh
tcpip_tcps_sc_unreachACCUMULATIONINT8The number of dropped TCP packet SYN cache due to ICMP unreachable.TCPIP.M563B4C62nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_TCPS

TCP packet data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_tcps_acceptsACCUMULATIONINT8The number of synchronize sequencenumbers (SYN) received in LISTEN state.TCPIP.M563B4C36nkmtbh, nkpmlbh
tcpip_tcps_badsynACCUMULATIONINT8The number of received acknowledgement for which this entity have no synchronize sequence numbers (SYN) in compressedstate.TCPIP.M563B4C53nkmtbh, nkpmlbh
tcpip_tcps_closedACCUMULATIONINT8The number of closed connections. Includesthe number of dropped connections(TCPS_DROPS M563B4C39).TCPIP.M563B4C38nkmtbh, nkpmlbh
tcpip_tcps_connattemptACCUMULATIONINT8The number of initiated connections, calls toconnect.TCPIP.M563B4C35nkmtbh, nkpmlbh
tcpip_tcps_conndropsACCUMULATIONINT8The number of TCP connections that havedropped before the synchronize sequencenumber (SYN) is received.TCPIP.M563B4C40nkmtbh, nkpmlbh
tcpip_tcps_connectsACCUMULATIONINT8The count of TCP connections that have beenestablished (actively or passively) includingaccepted connections(TCPIP_TCPS_ACCEPTS M563B4C36).TCPIP.M563B4C37nkmtbh, nkpmlbh
tcpip_tcps_delackACCUMULATIONINT8The number of sent delayed ACK- only(acknowledgement-only) TCP packets.TCPIP.M563B4C8nkmtbh, nkpmlbh
tcpip_tcps_dropsACCUMULATIONINT8The number of dropped TCP connectionsafter the synchronize sequence number(SYN) is received.TCPIP.M563B4C39nkmtbh, nkpmlbh
tcpip_tcps_keepdropsACCUMULATIONINT8The number of TCP connections dropped inkeep-alive, the connection established orawaiting synchronize sequence numbers(SYN).TCPIP.M563B4C48nkmtbh, nkpmlbh
tcpip_tcps_keepprobeACCUMULATIONINT8The number of keep-alive probes sent.TCPIP.M563B4C47nkmtbh, nkpmlbh
tcpip_tcps_keeptimeoACCUMULATIONINT8The number of times when the keep-alivetimer or the connection- establishment timerexpires.TCPIP.M563B4C46nkmtbh, nkpmlbh
tcpip_tcps_noportACCUMULATIONINT8The number of discarded TCP packets thatare dropped due to no socket.TCPIP.M563B4C52nkmtbh, nkpmlbh
tcpip_tcps_pawsdropACCUMULATIONINT8The number of TCP segments dropped due toPAWs (protection against wrapped sequencenumbers).TCPIP.M563B4C22nkmtbh, nkpmlbh
tcpip_tcps_pcbhashmissACCUMULATIONINT8The number of times when the protocolcontrol block (PCB) cache comparison fails.TCPIP.M563B4C51nkmtbh, nkpmlbh
tcpip_tcps_persisttimeoACCUMULATIONINT8The number of times that timer persistexpires.TCPIP.M563B4C45nkmtbh, nkpmlbh
tcpip_tcps_predackACCUMULATIONINT8The number of times when the TCP packetheader prediction is correct for ACKs(acknowledgements).TCPIP.M563B4C49nkmtbh, nkpmlbh
tcpip_tcps_preddatACCUMULATIONINT8The number of times when the TCP packetheader prediction is correct for the TCP datapackets.TCPIP.M563B4C50nkmtbh, nkpmlbh
tcpip_tcps_rcvackbyteACCUMULATIONINT8The number of received bytes acknowledgedby received ACK (acknowledgement) TCPpackets.TCPIP.M563B4C15nkmtbh, nkpmlbh
tcpip_tcps_rcvackpackACCUMULATIONINT8The number of received ACK(acknowledgement) TCP packets.TCPIP.M563B4C14nkmtbh, nkpmlbh
tcpip_tcps_rcvacktoomuchACCUMULATIONINT8The number of received ACKs(acknowledgements) for not sent TCP data(too much ACKs).TCPIP.M563B4C17nkmtbh, nkpmlbh
tcpip_tcps_rcvaftercloseACCUMULATIONINT8The number of packets received after that theconnection is closed.TCPIP.M563B4C31nkmtbh, nkpmlbh
tcpip_tcps_rcvbadoffACCUMULATIONINT8The number of received TCP packetsdiscarded due to invalid header offset fields,or invalid header length.TCPIP.M563B4C33nkmtbh, nkpmlbh
tcpip_tcps_rcvbadsumACCUMULATIONINT8The number of received TCP packetsdiscarded with checksum errors.TCPIP.M563B4C32nkmtbh, nkpmlbh
tcpip_tcps_rcvbyteafterwinACCUMULATIONINT8The number of received bytes beyondadvertised window.TCPIP.M563B4C28nkmtbh, nkpmlbh
tcpip_tcps_rcvbyteACCUMULATIONINT8The number of bytes received in a sequence.TCPIP.M563B4C19nkmtbh, nkpmlbh
tcpip_tcps_rcvdupackACCUMULATIONINT8The number of received duplicated ACK(acknowledgement) packets.TCPIP.M563B4C16nkmtbh, nkpmlbh
tcpip_tcps_rcvdupbyteACCUMULATIONINT8The number of received completely duplicatebytes.TCPIP.M563B4C21nkmtbh, nkpmlbh
tcpip_tcps_rcvduppackACCUMULATIONINT8The number of received completely duplicatepackets.TCPIP.M563B4C20nkmtbh, nkpmlbh
tcpip_tcps_rcvoobyteACCUMULATIONINT8The number of received out-of-order TCPbytes.TCPIP.M563B4C26nkmtbh, nkpmlbh
tcpip_tcps_rcvoopackACCUMULATIONINT8The number of received out-of-order TCPpackets.TCPIP.M563B4C25nkmtbh, nkpmlbh
tcpip_tcps_rcvpackafterwinACCUMULATIONINT8The number of received packets with somedata beyond advertised window.TCPIP.M563B4C27nkmtbh, nkpmlbh
tcpip_tcps_rcvpackACCUMULATIONINT8The number of packets received in asequence.TCPIP.M563B4C18nkmtbh, nkpmlbh
tcpip_tcps_rcvpartdupbyteACCUMULATIONINT8The number of duplicate bytes in partduplicatepackets.TCPIP.M563B4C24nkmtbh, nkpmlbh
tcpip_tcps_rcvpartduppackACCUMULATIONINT8The number of received TCP packets withsome duplicated data.TCPIP.M563B4C23nkmtbh, nkpmlbh
tcpip_tcps_rcvshortACCUMULATIONINT8The number of received TCP packetsdiscarded due to too short TCP packet.TCPIP.M563B4C34nkmtbh, nkpmlbh
tcpip_tcps_rcvtotalACCUMULATIONINT8Total number of received TCP packets.TCPIP.M563B4C13nkmtbh, nkpmlbh
tcpip_tcps_rcvwinprobeACCUMULATIONINT8The number of window probe packetsreceived.TCPIP.M563B4C29nkmtbh, nkpmlbh
tcpip_tcps_rcvwinupdACCUMULATIONINT8The number of received window update TCPpackets.TCPIP.M563B4C30nkmtbh, nkpmlbh
tcpip_tcps_rexmttimeoACCUMULATIONINT8The number of retransmit timeouts.TCPIP.M563B4C43nkmtbh, nkpmlbh
tcpip_tcps_rttupdatedACCUMULATIONINT8The number of times when Round trip time(RTT) estimators are updated.TCPIP.M563B4C41nkmtbh, nkpmlbh
tcpip_tcps_segstimedACCUMULATIONINT8The number of segments for which TCP triedto measure Round trip time (RTT).TCPIP.M563B4C42nkmtbh, nkpmlbh
tcpip_tcps_sndacksACCUMULATIONINT8The number of sent ACK- only(acknowledgement-only) TCP packets (datalength = 0).TCPIP.M563B4C7nkmtbh, nkpmlbh
tcpip_tcps_sndbyteACCUMULATIONINT8The number of TCP data bytes sent.TCPIP.M563B4C4nkmtbh, nkpmlbh
tcpip_tcps_sndctrlACCUMULATIONINT8The number of sent control (SYN, FIN, RST)TCP packets (data length = 0).TCPIP.M563B4C12nkmtbh, nkpmlbh
tcpip_tcps_sndpackACCUMULATIONINT8The number of TCP data packets sent (datalength greater than 0).TCPIP.M563B4C3nkmtbh, nkpmlbh
tcpip_tcps_sndprobeACCUMULATIONINT8The number of sent window probes. 1 byte ofdata forced by persist timer.TCPIP.M563B4C10nkmtbh, nkpmlbh
tcpip_tcps_sndrexmitbyteACCUMULATIONINT8The number of re-transmitted sent TCP databytes.TCPIP.M563B4C6nkmtbh, nkpmlbh
tcpip_tcps_sndrexmitpackACCUMULATIONINT8The number of re-transmitted sent TCP datapackets.TCPIP.M563B4C5nkmtbh, nkpmlbh
tcpip_tcps_sndtotalACCUMULATIONINT8The total number of sent TCP packets.TCPIP.M563B4C2nkmtbh, nkpmlbh
tcpip_tcps_sndurgACCUMULATIONINT8The number of TCP packets sent with UrgentPointer (URG) only (data length = 0).TCPIP.M563B4C9nkmtbh, nkpmlbh
tcpip_tcps_sndwinupACCUMULATIONINT8The number of sent window update-only TCPpackets (data length=0).TCPIP.M563B4C11nkmtbh, nkpmlbh
tcpip_tcps_timeoutdropACCUMULATIONINT8The number of TCP connections dropped in retransmission timeout.TCPIP.M563B4C44nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_UDP6S

TCP IP UDP version 6 data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_udp6s_badlenACCUMULATIONINT8The number of received UPDv6 datagrams not delivered due to data length larger than packet.TCPIP.M563B8C4nkmtbh, nkpmlbh
tcpip_udp6s_badsumACCUMULATIONINT8The number of received UPDv6 datagramsnot delivered due to checksum errors.TCPIP.M563B8C5nkmtbh, nkpmlbh
tcpip_udp6s_fullsockACCUMULATIONINT8Number of received UDPv6 datagrams notdelivered because input socket buffers arefull.TCPIP.M563B8C9nkmtbh, nkpmlbh
tcpip_udp6s_hdropsACCUMULATIONINT8The number of received UDPv6 datagrams not delivered due to packet shorter than header.TCPIP.M563B8C3nkmtbh, nkpmlbh
tcpip_udp6s_ipacketsACCUMULATIONINT8Total number of received UDP datagrams delivered to UDPv6 users.TCPIP.M563B8C2nkmtbh, nkpmlbh
tcpip_udp6s_noportmcastACCUMULATIONINT8The number of received UPDv6multicast/broadcast datagrams discarded dueto no process on destination port.TCPIP.M563B8C8nkmtbh, nkpmlbh
tcpip_udp6s_noportACCUMULATIONINT8The number of received UDPv6 packets withno process on destination port.TCPIP.M563B8C7nkmtbh, nkpmlbh
tcpip_udp6s_nosumACCUMULATIONINT8The number of received UDPv6 packetswithout checksum.TCPIP.M563B8C6nkmtbh, nkpmlbh
tcpip_udp6s_opacketsACCUMULATIONINT8Total number of UDPv6 datagrams sent.TCPIP.M563B8C11nkmtbh, nkpmlbh
tcpip_udp6s_pcbcachemissACCUMULATIONINT8The number of UPDv6 packets with ProcessControl Block (PCB) hash misses.TCPIP.M563B8C10nkmtbh, nkpmlbh


Processor.Nokia.GSM.TCPIP_UDPS

TCP IP UDP data.NB: this data has a secondary key of TCP/IP stack

The performance data measurements for this KPI group are recorded against the combination of Processor and TCPIP_Stack (tcpip_stack_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
tcpip_udps_badlenACCUMULATIONINT8The number of received UDP datagrams not delivered due to data length larger thanpacket.TCPIP.M563B5C4nkmtbh, nkpmlbh
tcpip_udps_badsumACCUMULATIONINT8The number of received UDP datagrams not delivered due to checksum errors.TCPIP.M563B5C5nkmtbh, nkpmlbh
tcpip_udps_fullsockACCUMULATIONINT8The number of received UDP datagrams not delivered because input socket buffers arefull.TCPIP.M563B5C8nkmtbh, nkpmlbh
tcpip_udps_hdropsACCUMULATIONINT8The number of received UDP datagrams not delivered due to packet shorter than header.TCPIP.M563B5C3nkmtbh, nkpmlbh
tcpip_udps_ipacketsACCUMULATIONINT8Total number of received UDP datagrams delivered to UDP users.TCPIP.M563B5C2nkmtbh, nkpmlbh
tcpip_udps_noportbcastACCUMULATIONINT8The number of received multicast/broad cast datagrams discarded due to no process ondestination port.TCPIP.M563B5C7nkmtbh, nkpmlbh
tcpip_udps_noportACCUMULATIONINT8The number of received UDP packets with no process on destination port.TCPIP.M563B5C6nkmtbh, nkpmlbh
tcpip_udps_opacketsACCUMULATIONINT8Total number of UDP datagrams sent.TCPIP.M563B5C10nkmtbh, nkpmlbh
tcpip_udps_pcbhashmissACCUMULATIONINT8The number of UPD packets with Process Control Block (PCB) hash misses.TCPIP.M563B5C9nkmtbh, nkpmlbh


RNC Performance Indicators

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


RNC.Nokia.GSM.Call_setup_service

Call setup service data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_successful_callsPERCENTAGEFLOATPercentage successful calls.percentok({cssmt_rnc_succ_bids}, ({cssmt_rnc_succ_bids} + {cssmt_rnc_failed_bids})) 
%_unsuccessful_callsPERCENTAGEINT8Percentage unsuccessful calls.percentfail({cssmt_rnc_failed_bids}, ({cssmt_rnc_succ_bids} + {cssmt_rnc_failed_bids})) 
cssmt_rnc_failed_bidsACCUMULATIONINT8Number of unsuccessful call setup service attempts in RNC level.CSSR.M387B4C6 
cssmt_rnc_failed_mean_timeACCUMULATIONINT8Mean time of unsuccessful call setup service attempts in seconds in ASCII reports and in 10 ms in XML reports. Mean time is calculated by dividing the value of the unsuccessful total call setup service time reservation by the value of unsuccessful call setup service attempts.CSSR.M387B4C7 
cssmt_rnc_succ_bidsACCUMULATIONINT8Number of successful call setup service attempts in the RNC level.CSSR.M387B4C4 
cssmt_rnc_succ_mean_timeACCUMULATIONINT8Mean time of successful call setup service attempts in seconds in ASCII reports and in 10 ms in XML reports. Mean time is calculated by dividing the value of the successful total call setup service time reservation by the value of successful call setup service attempts.CSSR.M387B4C5 


RNC.Nokia.GSM.Signalling_clear_code

Signalling clear code data.

The performance data measurements for this KPI group are recorded against the combination of RNC, MSC_Clear_Code (msc_clear_code_id) and Signal_Protocol (signal_protocol_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sscc_ringACCUMULATIONINT8The number of clear codes in the ringing phase (0...999999999).RNCMCC.M136B2C4 
sscc_signallingACCUMULATIONINT8The number of clear codes in the signalling phase (0...999999999).RNCMCC.M136B2C3 
sscc_speechACCUMULATIONINT8The number of clear codes in the speech phase (0...999999999).RNCMCC.M136B2C5 


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.Nokia.GSM.CDS_Circuit_Group

The results contain information about the number of seizures, successful calls, and congestion in the circuit group.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cgrcgroup_accepted_inACCUMULATIONINT8Number of successful call attempts (0...999999), clear codes 0...3FF. The field is updated when the first released circuit is released.CGRC.M16B2C12nkricbh, nkrocbh
cgrcgroup_accepted_outACCUMULATIONINT8Number of successful call attempts (0...999999), clear codes 0...3FF. The field is updated when the first released circuit is released.CGRC.M16B2C13nkricbh, nkrocbh
cgrcgroup_answered_inACCUMULATIONINT8Number of call attempts (0...999999) that have reached the conversation state. The field is updated when the first released circuit is released.CGRC.M16B2C16nkricbh, nkrocbh
cgrcgroup_answered_outACCUMULATIONINT8Number of call attempts (0...999999) that have reached the conversation state. The field is updated when the first released circuit is released.CGRC.M16B2C17nkricbh, nkrocbh
cgrcgroup_call_amount_inACCUMULATIONINT8Number of call attempts (0...999999) that have been started during the measurement period. The field is updated when the circuit is released.CGRC.M16B2C10nkricbh, nkrocbh
cgrcgroup_call_amount_outACCUMULATIONINT8Number of call attempts (0...999999) that have been started during the measurement period. The field is updated when the circuit is released.CGRC.M16B2C11nkricbh, nkrocbh
cgrcgroup_call_cong_x_100ACCUMULATIONINT8Number of call attempts (0...65535) terminated in call congestion. A call attempt terminates in call congestion if all the available circuits have already been reserved, or if the Automatic Congestion Control (ACC) or Selective Circuit Reservation (SCR) fCGRC.M16B2C9nkricbh, nkrocbh
cgrcgroup_corrupt_messageINTENSITYINTEGERIf record_count is zero (0), then tag is output (with value 1) along with the header informations, and no other data is processed.CGRC.M16B2C29nkricbh, nkrocbh
cgrcgroup_erlangs_in_x_100INTENSITYFLOATThe amount of traffic on the circuit group. That means the total reservation time of the object being measured in relation to the results accumulation period. The values are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the field can be greater than the value of the fields CRTS and AVECR.CGRC.M16B2C24nkricbh, nkrocbh
cgrcgroup_erlangs_inERLANGFLOATThe amount of traffic on the circuit group in erlangs (0.0...9999.9). That means the total reservation time of the object being measured in relation to the results accumulation period. The erlangs are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the ERLANGS field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the ERLANGS field can be greater than the value of the fields CRTS and AVECR.CGRC.M16B2C24 / 100nkricbh, nkrocbh
cgrcgroup_erlangs_out_x_100INTENSITYFLOATThe amount of traffic on the circuit group. That means the total reservation time of the object being measured in relation to the results accumulation period. The values are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the field can be greater than the value of the fields CRTS and AVECR.CGRC.M16B2C25nkricbh, nkrocbh
cgrcgroup_erlangs_outERLANGFLOATThe amount of traffic on the circuit group in erlangs (0.0...9999.9). That means the total reservation time of the object being measured in relation to the results accumulation period. The erlangs are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the ERLANGS field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the ERLANGS field can be greater than the value of the fields CRTS and AVECR.CGRC.M16B2C25 / 100nkricbh, nkrocbh
cgrcgroup_ext_fail_inACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in an error in the trunk circuit, clear codes 800...BFF. The field is updated when the first released circuit is released.CGRC.M16B2C22nkricbh, nkrocbh
cgrcgroup_ext_fail_outACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in an error in the trunk circuit, clear codes 800...BFF. The field is updated when the first released circuit is released.CGRC.M16B2C23nkricbh, nkrocbh
cgrcgroup_int_fail_inACCUMULATIONINT8Number of failed call attempts (0...65535) terminated in an error in the home exchange, clear codes 400...7FF. The field is updated when the first released circuit is released.CGRC.M16B2C20nkricbh, nkrocbh
cgrcgroup_int_fail_outACCUMULATIONINT8Number of failed call attempts (0...65535) terminated in an error in the home exchange, clear codes 400...7FF. The field is updated when the first released circuit is released.CGRC.M16B2C21nkricbh, nkrocbh
cgrcgroup_invalid_recordINTENSITYINTEGERTag appears at the end of the given counter group if the field value is 0xFF.CGRC.M16B2C28nkricbh, nkrocbh
cgrcgroup_min_freeINTENSITYINTEGERMinimum number of free circuits in the circuit group during the measurement period. The field is empty if the value is not available.CGRC.M16B2C27nkricbh, nkrocbh
cgrcgroup_nof_circuitsINTENSITYINTEGERNumber of circuits in the circuit groupCGRC.M16B2C3nkricbh, nkrocbh
cgrcgroup_nof_woex_crts_inINTENSITYINTEGERThe average number of circuits available (WO-EX) in the circuit group (0.0...4096.0). The field is empty if the value is not available.CGRC.M16B2C5nkricbh, nkrocbh
cgrcgroup_nof_woex_crts_outINTENSITYINTEGERThe average number of circuits available (WO-EX) in the circuit group (0.0...4096.0). The field is empty if the value is not available.CGRC.M16B2C6nkricbh, nkrocbh
cgrcgroup_subs_fail_inACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the first released circuit is released.CGRC.M16B2C18nkricbh, nkrocbh
cgrcgroup_subs_fail_outACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the first released circuit is released.CGRC.M16B2C19nkricbh, nkrocbh
cgrcgroup_timecong_percentx100INTENSITYFLOATTime congestion percentage (0.0...100.0) in the circuit group in relation to the results accumulation period. Principle of time congestion (TC) calculation: Time congestion in a circuit group is calculated in relation to the results accumulation period. Time congestion is calculated when all time slots available on the circuit group are in use, or the state of circuits prevents their use for outgoing traffic. Calculating time congestion is stopped when there are again time slots available (one or more calls are released, circuits are added, or the state of the circuit changes so that it becomes available for outgoing traffic). The field is only used for outgoing (OUT) circuit groups (including the OUT circuits in bidirectional circuit groups) (0.0...100.0%). The field is empty if the value is not available.CGRC.M16B2C7nkricbh, nkrocbh


Route_IF.Nokia.GSM.Circuit_Group_to_Destination

This measurement contains the measurement results from the circuit group to the destination measurements. N.B. There is a secondary key of number_destination

The performance data measurements for this KPI group are recorded against the combination of Route_IF and Number_Destination (number_destination_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ans_callsACCUMULATIONINT8Answered calls.CTD.M24B2C8nkrbmbh
avr_traf_erlangERLANGFLOATThe average traffic in erlangsCTD.M24B2C12 / 100.0nkrbmbh
ctd_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when the data provider in the signalling unit or the signalling unit(s) is restarted during the period and data might not be reliable.CTD.M24B2C15nkrbmbh
ctd_invalid_rec_foundINTENSITYINTEGERThe tag appears at the end of the given counter group with field value 1 when the actual record is invalid.CTD.M24B2C13nkrbmbh
ctd_overload_ctrl_actINTENSITYINTEGERThe tag appears at the end of the given counter group if the field value is 10 (In this case the Automatic Overload Control of Statistics has been activated.).CTD.M24B2C14nkrbmbh
ext_err_callsACCUMULATIONINT8Calls ended in the external error condition.CTD.M24B2C11nkrbmbh
int_err_callsACCUMULATIONINT8Calls ended in the internal error condition.CTD.M24B2C10nkrbmbh
nbr_callsACCUMULATIONINT8The number of attempts.CTD.M24B2C5nkrbmbh
subsc_errACCUMULATIONINT8The number of subscriber errors.CTD.M24B2C9nkrbmbh
succ_callsACCUMULATIONINT8The number of successful calls.CTD.M24B2C6nkrbmbh


Route_IF.Nokia.GSM.Circuit_Load

This measurement contains information about the load of the physical resources (circuit group) of the network element.

KPITypeData TypeDescriptionDerivationAdditional Summaries
average_available_circuitsINTENSITYFLOATThe average number of circuits (0.0...6553.5) available (in WO-EX state) in the circuit group / 10LOADM.M117B2C4 / 10nkrbmbh, nkrimbh, nkrombh
cgrl_avg_num_of_circuits_x10INTENSITYFLOATThe average number of circuits (0.0...6553.5) available (in WO-EX state) in the circuit group.LOADM.M117B2C4nkrbmbh, nkrimbh, nkrombh
cgrl_erlangs_x10ERLANGFLOATThe amount of traffic in Erlangs (0.0...99999.9), that is, the total seizure time of the object being measured in relation to the measurement period.LOADM.M117B2C10nkrbmbh, nkrimbh, nkrombh
cgrl_failure_rate_percent_x10INTENSITYFLOATCall failure rate in percents (0.0...100.0). The value is calculated by dividing the number of calls ended in internal or external failure by the total number of calls.LOADM.M117B2C5nkrbmbh, nkrimbh, nkrombh
cgrl_invalid_recordACCUMULATIONINT8Tag appears at the end of the given counter group if the field value is 1.LOADM.m117b2c11nkrbmbh, nkrimbh, nkrombh
cgrl_time_congest_percent_x10INTENSITYFLOATThe time congestion percentage.LOADM.M117B2C6nkrbmbh, nkrimbh, nkrombh
failed_calls_extACCUMULATIONINT8The number of calls ended in the external error condition.LOADM.M117B2C9nkrbmbh, nkrimbh, nkrombh
failed_calls_intACCUMULATIONINT8The number of calls ended in the internal error condition.LOADM.M117B2C8nkrbmbh, nkrimbh, nkrombh
failed_callsINTENSITYFLOATThe failed calls percentageLOADM.M117B2C5 / 10nkrbmbh, nkrimbh, nkrombh
number_of_circuitsINTENSITYINTEGERNumber of circuits in a circuit group.LOADM.M117B2C3nkrbmbh, nkrimbh, nkrombh
time_congestionINTENSITYFLOATThe time congestion percentage. /10LOADM.M117B2C6 / 10nkrbmbh, nkrimbh, nkrombh
total_callsACCUMULATIONINT8The total number of calls.LOADM.M117B2C7nkrbmbh, nkrimbh, nkrombh
traffic_intensityERLANGFLOATThe traffic intensity / 10LOADM.M117B2C10 / 10nkrbmbh, nkrimbh, nkrombh


Route_IF.Nokia.GSM.MSC_Circuit_Group

This measurement contains the measurement results from the circuit group measurements.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cgrcgroup_accepted_bothwayACCUMULATIONINT8incoming and outgoing traffic.{cgrcgroup_accepted_in} + {cgrcgroup_accepted_out}nkrbmbh, nkrimbh, nkrombh
cgrcgroup_accepted_inACCUMULATIONINT8Number of successful call attempts (0...999999), clear codes 0...3FF. The field is updated when the first released circuit is released.CGR.M16B2C12nkrbmbh, nkrimbh, nkrombh
cgrcgroup_accepted_outACCUMULATIONINT8Number of successful call attempts (0...999999), clear codes 0...3FF. The field is updated when the first released circuit is released.CGR.M16B2C13nkrbmbh, nkrimbh, nkrombh
cgrcgroup_answered_inACCUMULATIONINT8Number of call attempts (0...999999) that have reached the conversation state. The field is updated when the first released circuit is released.CGR.M16B2C16nkrbmbh, nkrimbh, nkrombh
cgrcgroup_answered_outACCUMULATIONINT8Number of call attempts (0...999999) that have reached the conversation state. The field is updated when the first released circuit is released.CGR.M16B2C17nkrbmbh, nkrimbh, nkrombh
cgrcgroup_call_amount_inACCUMULATIONINT8Number of call attempts (0...999999) that have been started during the measurement period. The field is updated when the circuit is released.CGR.M16B2C10nkrbmbh, nkrimbh, nkrombh
cgrcgroup_call_amount_outACCUMULATIONINT8Number of call attempts (0...999999) that have been started during the measurement period. The field is updated when the circuit is released.CGR.M16B2C11nkrbmbh, nkrimbh, nkrombh
cgrcgroup_call_cong_x_100ACCUMULATIONINT8Number of call attempts (0...65535) terminated in call congestion. A call attempt terminates in call congestion if all the available circuits have already been reserved, or if the Automatic Congestion Control (ACC) or Selective Circuit Reservation (SCR) fCGR.M16B2C9nkrbmbh, nkrimbh, nkrombh
cgrcgroup_corrupt_messageINTENSITYINTEGERIf record_count is zero (0), then tag is output (with value 1) along with the header informations, and no other data is processed.CGR.M16B2C29nkrbmbh, nkrimbh, nkrombh
cgrcgroup_data_prov_restartedACCUMULATIONINT8Tag appears with value 1 when data provider in signalling unit or signalling unit(s) is restarted during the period and data might not be reliable.CGR.M16B2C30nkrbmbh, nkrimbh, nkrombh
cgrcgroup_erlangs_in_x_100INTENSITYFLOATThe amount of traffic on the circuit group. That means the total reservation time of the object being measured in relation to the results accumulation period. The values are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the field can be greater than the value of the fields CRTS and AVECR.CGR.M16B2C24nkrbmbh, nkrimbh, nkrombh
cgrcgroup_erlangs_inERLANGFLOATThe amount of traffic on the circuit group in erlangs (0.0...9999.9). That means the total reservation time of the object being measured in relation to the results accumulation period. The erlangs are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the ERLANGS field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the ERLANGS field can be greater than the value of the fields CRTS and AVECR.CGR.M16B2C24 / 100nkrbmbh, nkrimbh, nkrombh
cgrcgroup_erlangs_out_x_100INTENSITYFLOATThe amount of traffic on the circuit group. That means the total reservation time of the object being measured in relation to the results accumulation period. The values are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the field can be greater than the value of the fields CRTS and AVECR.CGR.M16B2C25nkrbmbh, nkrimbh, nkrombh
cgrcgroup_erlangs_outERLANGFLOATThe amount of traffic on the circuit group in erlangs (0.0...9999.9). That means the total reservation time of the object being measured in relation to the results accumulation period. The erlangs are calculated from circuit seizure to circuit release. All of the circuit reservation time is updated in the results accumulation period in which the circuit is released. For this reason, remarkably large values in the ERLANGS field are possible in a case in which there are many calls that have started before the results accumulation period but that end in the results accumulation period. In such a case, the value in the ERLANGS field can be greater than the value of the fields CRTS and AVECR.CGR.M16B2C25 / 100nkrbmbh, nkrimbh, nkrombh
cgrcgroup_ext_fail_inACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in an error in the trunk circuit, clear codes 800...BFF. The field is updated when the first released circuit is released.CGR.M16B2C22nkrbmbh, nkrimbh, nkrombh
cgrcgroup_ext_fail_outACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in an error in the trunk circuit, clear codes 800...BFF. The field is updated when the first released circuit is released.CGR.M16B2C23nkrbmbh, nkrimbh, nkrombh
cgrcgroup_int_fail_inACCUMULATIONINT8Number of failed call attempts (0...65535) terminated in an error in the home exchange, clear codes 400...7FF. The field is updated when the first released circuit is released.CGR.M16B2C20nkrbmbh, nkrimbh, nkrombh
cgrcgroup_int_fail_outACCUMULATIONINT8Number of failed call attempts (0...65535) terminated in an error in the home exchange, clear codes 400...7FF. The field is updated when the first released circuit is released.CGR.M16B2C21nkrbmbh, nkrimbh, nkrombh
cgrcgroup_invalid_recordINTENSITYINTEGERTag appears at the end of the given counter group if the field value is 0xFF.CGR.M16B2C28nkrbmbh, nkrimbh, nkrombh
cgrcgroup_min_freeINTENSITYINTEGERMinimum number of free circuits in the circuit group during the measurement period. The field is empty if the value is not available.CGR.M16B2C27nkrbmbh, nkrimbh, nkrombh
cgrcgroup_nof_circuitsINTENSITYINTEGERNumber of circuits in the circuit groupCGR.M16B2C3nkrbmbh, nkrimbh, nkrombh
cgrcgroup_nof_woex_crts_inINTENSITYINTEGERThe average number of circuits available (WO-EX) in the circuit group (0.0...4096.0). The field is empty if the value is not available.CGR.M16B2C5nkrbmbh, nkrimbh, nkrombh
cgrcgroup_nof_woex_crts_outINTENSITYINTEGERThe average number of circuits available (WO-EX) in the circuit group (0.0...4096.0). The field is empty if the value is not available.CGR.M16B2C6nkrbmbh, nkrimbh, nkrombh
cgrcgroup_ring_inACCUMULATIONINT8Number of call attempts (0...999999) that have reached the ringing phase. When MSS receives the ACM message from the other MSS, Statistics saves that the call has reached the ringing phase.CGR.M16B2C31nkrbmbh, nkrimbh, nkrombh
cgrcgroup_ring_outACCUMULATIONINT8Number of call attempts (0...999999) that have reached the ringing phase. When MSS receives the ACM message from the other MSS, Statistics saves that the call has reached the ringing phase.CGR.M16B2C32nkrbmbh, nkrimbh, nkrombh
cgrcgroup_subs_fail_inACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the first released circuit is released.CGR.M16B2C18nkrbmbh, nkrimbh, nkrombh
cgrcgroup_subs_fail_outACCUMULATIONINT8Number of failed call attempts (0...65535) that have terminated in a subscriber error, clear codes C00...FFF. The field is updated when the first released circuit is released.CGR.M16B2C19nkrbmbh, nkrimbh, nkrombh
cgrcgroup_timecong_percentx100INTENSITYFLOATTime congestion percentage (0.0...100.0) in the circuit group in relation to the results accumulation period. Principle of time congestion (TC) calculation: Time congestion in a circuit group is calculated in relation to the results accumulation period. TCGR.M16B2C7nkrbmbh, nkrimbh, nkrombh


Route_IF.Nokia.GSM.Priority_calls

Priority call data

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_nsep_callsPERCENTAGEFLOATPercentage successful callspercentok({nsep_calls}, {nsep_attempts})nkrbmbh
nsep_abandonACCUMULATIONINT8Total number of times when PRIORITY calls are removed from the trunk group because the MS has disconnected the call, the radio contact with the MS has been lost, or a release message is received on the incoming ISUP trunk (counter 0.23).PRCAR.M392B4C8nkrbmbh
nsep_attemptsACCUMULATIONINT8Total number of outgoing PRIORITY Call Attempts which require an outgoing trunk on the specified route /trunk group/ (counter 0.18).PRCAR.M392B4C3nkrbmbh
nsep_callsACCUMULATIONINT8Total number of outgoing PRIORITY Calls for which trunks are successfully set up to a succeeding switch on the specified route/trunk group/ (counter 0.19).PRCAR.M392B4C4nkrbmbh
nsep_overflowACCUMULATIONINT8Total number of outgoing PRIORITY Calls that fail to queue because the maximum trunk queue length has been reached on the specified route /trunk group/ (counter 0.21).PRCAR.M392B4C6nkrbmbh
nsep_queuedACCUMULATIONINT8Total number of outgoing PRIORITY Calls that are queued for a trunk on the specified route /trunk group/ (counter 0.20).PRCAR.M392B4C5nkrbmbh
nsep_time_outACCUMULATIONINT8Total number of times when PRIORITY calls are removed from a trunk queue because the call exceeded the maximum trunk queue time on the specified route (counter 0.22).PRCAR.M392B4C7nkrbmbh
wps_attemptsACCUMULATIONINT8Total number of outgoing WPS Call Attempts, which require an outgoing trunk on the specified route /trunk group/ (counter 0.17).PRCAR.M392B4C2nkrbmbh


Route_IF.Nokia.GSM.Routing_Component

This section describes the field reporting of routing components measurement.

KPITypeData TypeDescriptionDerivationAdditional Summaries
rout_bound_rateINTENSITYFLOATThe highest possible passed call rate (per second) for a gapping gate (0...9999).ROUTDM.M137B3C4 
rout_dx_errorINTENSITYINTEGERMessage status field includes error code.ROUTDM.M137B3C7 
rout_gapped_callsACCUMULATIONINT8Number of gapped events.ROUTDM.M137B3C3 
rout_gcrINTENSITYFLOATPercentage ratio (0...100.0%) of gapped events to the total number of events.ROUTDM.M137B3C6 
rout_in_callsACCUMULATIONINT8Number of events.ROUTDM.M137B3C1 
rout_match_callsACCUMULATIONINT8Number of successful events.ROUTDM.M137B3C2 
rout_perm_attr_data_changedINTENSITYINTEGERTag appears with value 1 when the permanent data of the attribute has been changed during result accumulation periodROUTDM.M137B3C8 
rout_token_bankINTENSITYINTEGERToken bank size (0...65280)ROUTDM.M137B3C5 


Route_IF.Nokia.GSM.Setups

CSTS CGR Setup data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
csts_cgr_long_setups_inACCUMULATIONINT8Number of incoming successful setups in the CGR, when the setup time is over the setup time defined by PRFILE parameter.CSTSC.M386B3C5nkrbmbh, nkrimbh, nkrombh
csts_cgr_long_setups_outACCUMULATIONINT8Number of outgoing successful setups in the CGR, when the setup time is over the setup time defined by PRFILE parameter.CSTSC.M386B3C10nkrbmbh, nkrimbh, nkrombh
csts_cgr_max_succ_setup_inACCUMULATIONINT8Longest setup time in the CGR for incoming direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 millisecondsCSTSC.M386B3C7nkrbmbh, nkrimbh, nkrombh
csts_cgr_max_succ_setup_outACCUMULATIONINT8The longest setup time in the CGR for outgoing direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSC.M386B3C12nkrbmbh, nkrimbh, nkrombh
csts_cgr_min_succ_setup_inACCUMULATIONINT8Shortest setup time in the CGR for incoming direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSC.M386B3C6nkrbmbh, nkrimbh, nkrombh
csts_cgr_min_succ_setup_outACCUMULATIONINT8The shortest setup time in the CGR for outgoing direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSC.M386B3C11nkrbmbh, nkrimbh, nkrombh
csts_cgr_setup_ave_inACCUMULATIONINT8Average setup time in the CGR for incoming direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 milliseconds.CSTSC.M386B3C8nkrbmbh, nkrimbh, nkrombh
csts_cgr_setup_e_outACCUMULATIONINT8The average time of the durations of the successful setups in the CGR for outgoing direction during the period. The unit of time in ASCII report is seconds, and in XML reports it is 10 millisecondsCSTSC.M386B3C13nkrbmbh, nkrimbh, nkrombh
csts_cgr_setups_inACCUMULATIONINT8Number of all incoming successful setups in a specified CGR during the report period.CSTSC.M386B3C4nkrbmbh, nkrimbh, nkrombh
csts_cgr_setups_outACCUMULATIONINT8Number of all outgoing successful setups in specified CGR during the report period.CSTSC.M386B3C9nkrbmbh, nkrimbh, nkrombh


Route_IF.Nokia.GSM.Signal_Clear_Code_Ckt_Group

Signalling-specific clear code measurements

The performance data measurements for this KPI group are recorded against the combination of Route_IF, MSC_Clear_Code (msc_clear_code_id) and Signal_Protocol (signal_protocol_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
calls_in_ringACCUMULATIONINT8The number of calls ending with clear code in ring phaseCGRCC.M136B2C4 
calls_in_signalACCUMULATIONINT8The number of calls ending with clear code in signalling phaseCGRCC.M136B2C3 
calls_in_speechACCUMULATIONINT8The number of calls ending with clear code in speech phaseCGRCC.M136B2C5 


Route_IF.Nokia.GSM.Traffic

Route traffic data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_route_accepPERCENTAGEFLOATPercentage calls accepted.percentok({route_accep}, {route_attempt}) 
route_accepACCUMULATIONINT8The counter shows amount of calls on the given route that were ended with clear code 00x3FF.ROU.M391B2C6 
route_answerACCUMULATIONINT8The counter shows amount of calls on the given route that were answered.ROU.M391B2C7 
route_attemptACCUMULATIONINT8The counter shows the amount of routing attempts on the given route.ROU.M391B2C4 
route_congrelACCUMULATIONINT8Number of unsuccessful routing attempts,which were unsuccessful because of congestion, and the call was released, that is, there is no other alternative route possibility .ROU.M391B2C16 
route_craACCUMULATIONINT8Number of unsuccessful routing attempts,which were unsuccessful because of congestion.ROU.M391B2C14 
route_data_prov_restartedACCUMULATIONINT8Counter is printed with value 1 if the data provider in signalling unit or the signalling unit is restarted during the measurement period, otherwise, the counter is omitted.ROU.M391B2C13 
route_efailACCUMULATIONINT8The counter shows the amount of calls on the given route that were ended with clear code 0x8000xBFF.ROU.M391B2C10 
route_erlangs_x100ERLANGFLOATThe counter shows the erlang value of all attempts on the given route, when circuit reservation was made. Erlang is calculated on the basis of circuit reservation.ROU.M391B2C11 
route_ifailACCUMULATIONINT8The counter shows the amount of calls on the given route that were ended with clear code 0x4000x7FF.ROU.M391B2C9 
route_invalid_recordACCUMULATIONINT8Counter is printed with value 1 if the measurement record was corrupted during the measurement period, otherwise, the counter is omitted. If SUBDEST in localMoid was UNKNOWN, then whole record was corrupted, else only that route was corrupted.ROU.M391B2C12 
route_sfailACCUMULATIONINT8The counter shows the amount of calls on the given route that were ended with clear code 0xC000xFFFROU.M391B2C8 
route_urarelACCUMULATIONINT8Number of unsuccessful routing attempts,which were unsuccessful for any reason, and the call was released,that is, there is no other alternative route possibility.ROU.M391B2C15 
route_uraACCUMULATIONINT8The counter shows unsuccessful Routing Attempts. Those cases are counted here, where no circuit reservation was possible on the given route because, for example, congestion has happened.ROU.M391B2C5 


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.Nokia.GSM.HLR_Signalling_Link_Avail_2

Signalling link availability measurements for HLR node

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to local management actionsSLAHLR.M208B2C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_inhibit_rem_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to remote management actionsSLAHLR.M208B2C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_local_busy_atmACCUMULATIONINT8Duration of local busy (ATM) (2.15 in ITU-T Q.752).SLAHLR.M208B2C16nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_local_busyACCUMULATIONINT8Duration of local busy (number of SIBs).SLAHLR.M208B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_unavail_link_failureACCUMULATIONINT8Duration of signalling link unavailability due to link failureSLAHLR.M208B2C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_unavail_local_blockingACCUMULATIONINT8Duration of signalling link unavailability due to local blockingSLAHLR.M208B2C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_unavail_rem_proc_outageACCUMULATIONINT8Duration of signalling link unavailability due to remote processor outageSLAHLR.M208B2C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_of_unavailACCUMULATIONINT8Duration of signalling link unavailability for any reasonSLAHLR.M208B2C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
loc_manag_inhibitACCUMULATIONINT8Local management inhibit.SLAHLR.M208B2C12nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
loc_manag_uninhibitedACCUMULATIONINT8Local management uninhibit.SLAHLR.M208B2C13nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
local_manual_changeoversACCUMULATIONINT8Local manual changeovers and changeovers due to system recovery actions.SLAHLR.M208B2C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
rem_inhibitACCUMULATIONINT8Start of remote inhibition.SLAHLR.M208B2C14nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
rem_proc_outage_startACCUMULATIONINT8Start of remote processor outage.SLAHLR.M208B2C10nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
rem_proc_outage_stopACCUMULATIONINT8Stop of remote processor outage.SLAHLR.M208B2C11nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
rem_uninhibitedACCUMULATIONINT8End of remote inhibition.SLAHLR.M208B2C15nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
remote_initiative_changeoversACCUMULATIONINT8Remote initiative changeovers.SLAHLR.M208B2C9nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh


Signalling_Link.Nokia.GSM.HLR_Signalling_Link_Availability

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_local_busy_atmACCUMULATIONINT8Duration of local busy (ATM) (2.15 in ITU-T Q.752).SLHLR.M208B2C16nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_local_busyACCUMULATIONINT8The duration of local busy. SLHLR.M208B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_unavail_anyACCUMULATIONINT8Duration of signalling link unavailability for any reason SLHLR.M208B2C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_unavail_linkACCUMULATIONINT8Duration of signalling link unavailability due to link failure SLHLR.M208B2C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_unavail_local_blockACCUMULATIONINT8Duration of signalling link unavailability due to local blocking SLHLR.M208B2C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_unavail_local_mngACCUMULATIONINT8Duration of signalling link inhibition due to local management actions SLHLR.M208B2C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_unavail_remote_cpuACCUMULATIONINT8Duration of signalling link unavailability due to remote processor outage SLHLR.M208B2C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_unavail_remote_mngACCUMULATIONINT8Duration of signalling link inhibition due to remote management actions SLHLR.M208B2C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
local_busyACCUMULATIONINT8Duration of local busy (number of SIBs).SLHLR.M208B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
local_management1ACCUMULATIONINT8Local management inhibit.SLHLR.M208B2C12nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
local_management2ACCUMULATIONINT8Local management uninhibit.SLHLR.M208B2C13nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
local_manual_coACCUMULATIONINT8Local manual changeovers and changeovers due to system recovery actions.SLHLR.M208B2C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
remote_coACCUMULATIONINT8Remote initiative changeovers.SLHLR.M208B2C9nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
remote_inhibit_endACCUMULATIONINT8End of remote inhibition.SLHLR.M208B2C15nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
remote_inhibit_startACCUMULATIONINT8Start of remote inhibition.SLHLR.M208B2C14nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
start_remote_cpuACCUMULATIONINT8Start of remote processor outage.SLHLR.M208B2C10nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
stop_remote_cpuACCUMULATIONINT8Stop of remote processor outage.SLHLR.M208B2C11nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh


Signalling_Link.Nokia.GSM.HLR_Signalling_Link_Performance

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
auto_coACCUMULATIONINT8Automatic changeover.SLPHLR.M209B3C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
automatic_changebacksACCUMULATIONINT8Automatic changeback (1.11 in ITU-T Q.752)SLPHLR.M209B3C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_in_serviceACCUMULATIONINT8In-service time of the signalling link during the reporting period.SLPHLR.M209B2C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failure_abnormalACCUMULATIONINT8Signalling link failure - abnormal FIBR/BSNR.SLPHLR.M209B2C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failure_ackACCUMULATIONINT8Signalling link failure - excessive delay.SLPHLR.M209B2C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failure_alignmentACCUMULATIONINT8Signalling link alignment or proving failure.SLPHLR.M209B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failure_allACCUMULATIONINT8Signalling link failures - all reasons.SLPHLR.M209B2C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failure_congACCUMULATIONINT8Signalling link failure - excessive duration.SLPHLR.M209B2C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failure_error_rateACCUMULATIONINT8Signalling link failure - excessive error rate.SLPHLR.M209B2C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_restoreACCUMULATIONINT8Signalling link restoration.SLPHLR.M209B3C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
maa_errorACCUMULATIONINT8MAA-ERROR indication with Error Type SD loss. SLPHLR.M209B2C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
negative_ackACCUMULATIONINT8The number of negative acknowledgements received.SLPHLR.M209B3C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
signal_unitsACCUMULATIONINT8The number of signal units received in error.SLPHLR.M209B3C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh


Signalling_Link.Nokia.GSM.HLR_Signalling_Link_Utilisation

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cong1ACCUMULATIONINT8Signalling link congestion (level 1).MTPHLR.M210B2C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
cong2ACCUMULATIONINT8Signalling link congestion (level 2).MTPHLR.M210B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
cong3ACCUMULATIONINT8Signalling link congestion (level 3).MTPHLR.M210B2C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_cong1ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 1).MTPHLR.M210B2C15nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_cong2ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 2).MTPHLR.M210B2C16nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
duration_cong3ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 3).MTPHLR.M210B2C17nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
inc_30_peak_cong_start_timeACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedMTPHLR.M210B3C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
inc_30_peak_load_erlangERLANGFLOATPeak load for incoming traffic during a 30-minute period.MTPHLR.M210B3C1 / 1000nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
inc_5_peak_cong_start_timeACCUMULATIONINT8Start time of the 5-minute freezing period when the peak congestion for the incoming traffic was noticedMTPHLR.M210B3C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
inc_5_peak_load_erlangERLANGFLOATPeak load during a 5-minute period.MTPHLR.M210B3C5 / 1000nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
incoming_utilisationACCUMULATIONFLOATIncoming utilisation of the signalling linkif MTPHLR.M210B1C2 < 1 then 100 else (M210B2C2 + 6 * (M210B2C4 * 8)) / ((interval*60) * M210B1C2)nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msg_receivedACCUMULATIONINT8The number of message signal units received.MTPHLR.M210B2C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msg_transACCUMULATIONINT8The number of message signal units transmitted.MTPHLR.M210B2C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msu_discarded_cong1ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 1).MTPHLR.M210B2C9nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msu_discarded_cong2ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 2).MTPHLR.M210B2C10nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msu_discarded_cong3ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 3).MTPHLR.M210B2C11nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msu_loss_cong1ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 1).MTPHLR.M210B2C12nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msu_loss_cong2ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 2).MTPHLR.M210B2C13nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msu_loss_cong3ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 3).MTPHLR.M210B2C14nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
out_30_peak_cong_start_timeACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPHLR.M210B3C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
out_30_peak_load_erlangERLANGFLOATPeak load for outgoing traffic during a 30-minute period.MTPHLR.M210B3C3 / 1000nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
out_5_peak_cong_start_timeACCUMULATIONINT8Start time of the 5-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPHLR.M210B3C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
out_5_peak_load_erlangERLANGFLOATPeak load for incoming traffic during a 5-minute period.MTPHLR.M210B3C7 / 1000nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
outgoing_utilisationACCUMULATIONFLOATOutgoing utilisation of the signalling linkif MTPHLR.M210B1C2 < 1 then 100 else (M210B2C1 + 6 * (M210B2C3 * 8)) / ((interval*60) * M210B1C2)nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
retransmitsACCUMULATIONINT8The number of octets retransmitted.MTPHLR.M210B2C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sif_sio_receivedACCUMULATIONINT8The number of received SIF and SIO octetsMTPHLR.M210B2C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sif_sio_transACCUMULATIONINT8The number of SIF and SIO octets transmitted.MTPHLR.M210B2C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh


Signalling_Link.Nokia.GSM.HLR_Signalling_point_perform_2

Signalling link performance for HLR node

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changebacksACCUMULATIONINT8Automatic changebackSLPNHLR.M209B3C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
automatic_changeoversACCUMULATIONINT8Automatic changeoverSLPNHLR.M209B3C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
dur_in_service_stateACCUMULATIONINT8Duration of signalling link in the in-service stateSLPNHLR.M209B2C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8Signalling link failure - abnormal FIBR/BSNRSLPNHLR.M209B2C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_ali_or_prov_failACCUMULATIONINT8Signalling link alignment or proving failureSLPNHLR.M209B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_all_reasonsACCUMULATIONINT8Signalling link failures - all reasonsSLPNHLR.M209B2C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_exc_del_of_ackACCUMULATIONINT8Caused by excessive delay of acknowledgementSLPNHLR.M209B2C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_exc_dur_of_congACCUMULATIONINT8Signalling link failure - excessive duration of congestionSLPNHLR.M209B2C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_exc_error_rateACCUMULATIONINT8Signalling link failure - excessive error rateSLPNHLR.M209B2C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_failures_m_err_ind_sd_losACCUMULATIONINT8MAA-ERROR indication with Error Type SD lossSLPNHLR.M209B2C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
link_restorationsACCUMULATIONINT8Signalling link restorationSLPNHLR.M209B3C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
negative_acksACCUMULATIONINT8Number of negative acknowledgements receivedSLPNHLR.M209B3C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sign_units_received_in_errorACCUMULATIONINT8Number of signal units received in errorSLPNHLR.M209B3C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh


Signalling_Link.Nokia.GSM.HLR_Signalling_Point_Util_2

Signalling link utilisation for HLR node

KPITypeData TypeDescriptionDerivationAdditional Summaries
BIT_RATEINTENSITYINTEGERThe type of the link, TDM=0 or ATM=1.MTPNHLR.M210B1C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
cumulative_duration_level1ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 1).MTPNHLR.M210B2C15nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
cumulative_duration_level2ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 2).MTPNHLR.M210B2C16nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
cumulative_duration_level3ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 3).MTPNHLR.M210B2C17nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
events_res_in_loss_of_msus_l1ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 1).MTPNHLR.M210B2C12nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
events_res_in_loss_of_msus_l2ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 2).MTPNHLR.M210B2C13nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
events_res_in_loss_of_msus_l3ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 3).MTPNHLR.M210B2C14nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
incoming_utilisationACCUMULATIONFLOATIncoming utilisation of the signalling linkif MTPNHLR.M210B1C2 < 1 then 100 else (M210B2C2 + 6 * (M210B2C4 * 8)) / ((interval*60) * M210B1C2)nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_30_peak_traf_in_startedACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedMTPNHLR.M210B3C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_30_peak_traf_out_startedACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPNHLR.M210B3C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_30_peakload_traffic_inERLANGINT830 minutes peak load in milliErlangs for incoming trafficMTPNHLR.M210B3C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_30_peakload_traffic_outERLANGINT830 minutes peak load in milliErlangs for outgoing trafficMTPNHLR.M210B3C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_5_peak_traf_in_startedACCUMULATIONINT8Start time of the 5 minutes freezing period when the peak congestion for incoming traffic was noticed (Measured as minutes from measurement period start time.)MTPNHLR.M210B3C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_5_peak_traf_out_startedACCUMULATIONINT8Start time of the 5 minutes freezing period when the peak congestion for outgoing traffic was noticed. (Measured as minutes from measurement period start time.)MTPNHLR.M210B3C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_5_peakload_traffic_inERLANGINT85 minutes peak load in milliErlangs for incoming trafficMTPNHLR.M210B3C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
min_5_peakload_traffic_outERLANGINT85 minutes peak load in milliErlangs for outgoing trafficMTPNHLR.M210B3C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msus_discarded_level1ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 1).MTPNHLR.M210B2C9nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msus_discarded_level2ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 2).MTPNHLR.M210B2C10nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msus_discarded_level3ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 3).MTPNHLR.M210B2C11nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msus_receivedACCUMULATIONINT8The number of message signal units received.MTPNHLR.M210B2C4nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
msus_transmittedACCUMULATIONINT8The number of message signal units transmitted.MTPNHLR.M210B2C3nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
octets_retransmittedACCUMULATIONINT8The number of octets retransmitted.MTPNHLR.M210B2C5nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
outgoing_utilisationACCUMULATIONFLOATOutgoing utilisation of the signalling linkif MTPNHLR.M210B1C2 < 1 then 100 else (M210B2C1 + 6 * (M210B2C3 * 8)) / ((interval*60) * M210B1C2)nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sif_and_sio_octets_receivedACCUMULATIONINT8The number of received SIF and SIO octetsMTPNHLR.M210B2C2nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sif_and_sio_octets_transmittedACCUMULATIONINT8The number of SIF and SIO octets transmitted.MTPNHLR.M210B2C1nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sl_congestion_level1ACCUMULATIONINT8Signalling link congestion (level 1).MTPNHLR.M210B2C6nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sl_congestion_level2ACCUMULATIONINT8Signalling link congestion (level 2).MTPNHLR.M210B2C7nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh
sl_congestion_level3ACCUMULATIONINT8Signalling link congestion (level 3).MTPNHLR.M210B2C8nkslhlrxbh, nkslhltxbh, nkslhrxbh, nkslhtxbh


Signalling_Link.Nokia.GSM.MSC_Signalling_Link_Avail_2

Signalling link availability measurements for MSC node

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to local management actionsSLAMSC.M208B2C5nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_inhibit_rem_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to remote management actionsSLAMSC.M208B2C6nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_local_busy_atmACCUMULATIONINT8Duration of local busy (ATM) (2.15 in ITU-T Q.752).SLAMSC.M208B2C16nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_local_busyACCUMULATIONINT8Duration of local busy (number of SIBs).SLAMSC.M208B2C7nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_unavail_link_failureACCUMULATIONINT8Duration of signalling link unavailability due to link failureSLAMSC.M208B2C2nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_unavail_local_blockingACCUMULATIONINT8Duration of signalling link unavailability due to local blockingSLAMSC.M208B2C3nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_unavail_rem_proc_outageACCUMULATIONINT8Duration of signalling link unavailability due to remote processor outageSLAMSC.M208B2C4nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_of_unavailACCUMULATIONINT8Duration of signalling link unavailability for any reasonSLAMSC.M208B2C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
loc_manag_inhibitACCUMULATIONINT8Local management inhibit.SLAMSC.M208B2C12nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
loc_manag_uninhibitedACCUMULATIONINT8Local management uninhibit.SLAMSC.M208B2C13nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
local_manual_changeoversACCUMULATIONINT8Local manual changeovers and changeovers due to system recovery actions.SLAMSC.M208B2C8nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
rem_inhibitACCUMULATIONINT8Start of remote inhibition.SLAMSC.M208B2C14nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
rem_proc_outage_startACCUMULATIONINT8Start of remote processor outage.SLAMSC.M208B2C10nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
rem_proc_outage_stopACCUMULATIONINT8Stop of remote processor outage.SLAMSC.M208B2C11nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
rem_uninhibitedACCUMULATIONINT8End of remote inhibition.SLAMSC.M208B2C15nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
remote_initiative_changeoversACCUMULATIONINT8Remote initiative changeovers.SLAMSC.M208B2C9nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh


Signalling_Link.Nokia.GSM.MSC_Signalling_Link_Availability

This measurement contains measurement data of one or more MTP signalling inks.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_local_busy_atmACCUMULATIONINT8Duration of local busy (ATM) (2.15 in ITU-T Q.752).SLMSC.M208B2C16nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_unavail_anyACCUMULATIONINT8Duration of signalling link unavailability for any reason SLMSC.M208B2C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_unavail_linkACCUMULATIONINT8Duration of signalling link unavailability due to link failure SLMSC.M208B2C2nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_unavail_local_blockACCUMULATIONINT8Duration of signalling link unavailability due to local blocking SLMSC.M208B2C3nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_unavail_local_mngACCUMULATIONINT8Duration of signalling link inhibition due to local management actions SLMSC.M208B2C5nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_unavail_remote_cpuACCUMULATIONINT8Duration of signalling link unavailability due to remote processor outage SLMSC.M208B2C4nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_unavail_remote_mngACCUMULATIONINT8Duration of signalling link inhibition due to remote management actions SLMSC.M208B2C6nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
local_busyACCUMULATIONINT8Duration of local busy (number of SIBs).SLMSC.M208B2C7nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
local_management1ACCUMULATIONINT8Local management inhibit.SLMSC.M208B2C12nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
local_management2ACCUMULATIONINT8Local management uninhibit.SLMSC.M208B2C13nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
local_manual_coACCUMULATIONINT8Local manual changeovers and changeovers due to system recovery actions.SLMSC.M208B2C8nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
remote_coACCUMULATIONINT8Remote initiative changeovers.SLMSC.M208B2C9nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
remote_inhibit_endACCUMULATIONINT8End of remote inhibition.SLMSC.M208B2C15nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
remote_inhibit_startACCUMULATIONINT8Start of remote inhibition.SLMSC.M208B2C14nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
start_remote_cpuACCUMULATIONINT8Start of remote processor outage.SLMSC.M208B2C10nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
stop_remote_cpuACCUMULATIONINT8Stop of remote processor outage.SLMSC.M208B2C11nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh


Signalling_Link.Nokia.GSM.MSC_Signalling_Link_Performance

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
auto_cbACCUMULATIONINT8Automatic changeback.SLPMSC.M209B3C4nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
auto_coACCUMULATIONINT8Automatic changeover.SLPMSC.M209B3C3nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_in_serviceACCUMULATIONINT8In-service time of the signalling link during the reporting period.SLPMSC.M209B2C1nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failure_abnormalACCUMULATIONINT8Signalling link failure - abnormal FIBR/BSNR.SLPMSC.M209B2C3nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failure_ackACCUMULATIONINT8Signalling link failure - excessive delay.SLPMSC.M209B2C4nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failure_alignmentACCUMULATIONINT8Signalling link alignment or proving failure.SLPMSC.M209B2C7nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failure_allACCUMULATIONINT8Signalling link failures - all reasons.SLPMSC.M209B2C2nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failure_congACCUMULATIONINT8Signalling link failure - excessive duration.SLPMSC.M209B2C6nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failure_error_rateACCUMULATIONINT8Signalling link failure - excessive error rate.SLPMSC.M209B2C5nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_restoreACCUMULATIONINT8Signalling link restoration.SLPMSC.M209B3C5nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
maa_errorACCUMULATIONINT8MAA-ERROR indication with Error Type SD loss. SLPMSC.M209B2C8nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
negative_ackACCUMULATIONINT8The number of negative acknowledgements received.SLPMSC.M209B3C2nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
signal_unitsACCUMULATIONINT8The number of signal units received in error.SLPMSC.M209B3C1nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh


Signalling_Link.Nokia.GSM.MSC_Signalling_Link_Utilisation

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cong1ACCUMULATIONINT8Signalling link congestion (level 1).MTPMSC.M210B2C6nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
cong2ACCUMULATIONINT8Signalling link congestion (level 2).MTPMSC.M210B2C7nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
cong3ACCUMULATIONINT8Signalling link congestion (level 3).MTPMSC.M210B2C8nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_cong1ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 1).MTPMSC.M210B2C15nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_cong2ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 2).MTPMSC.M210B2C16nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
duration_cong3ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 3).MTPMSC.M210B2C17nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
inc_30_peak_cong_start_timeACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedMTPMSC.M210B3C2nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
inc_30_peak_load_erlangERLANGFLOATPeak load for incoming traffic during a 30-minute period.MTPMSC.M210B3C1 / 1000nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
inc_5_peak_cong_start_timeACCUMULATIONINT8Start time of the 5-minute freezing period when the peak congestion for the incoming traffic was noticedMTPMSC.M210B3C6nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
inc_5_peak_load_erlangERLANGFLOATPeak load during a 5-minute period.MTPMSC.M210B3C5 / 1000nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
incoming_utilisationACCUMULATIONFLOATIncoming utilisation of the signalling linkif MTPMSC.M210B1C2 < 1 then 100 else (M210B2C2 + 6 * (M210B2C4 * 8)) / ((interval*60) * M210B1C2)nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msg_receivedACCUMULATIONINT8The number of message signal units received.MTPMSC.M210B2C4nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msg_transACCUMULATIONINT8The number of message signal units transmitted.MTPMSC.M210B2C3nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msu_discarded_cong1ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 1).MTPMSC.M210B2C9nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msu_discarded_cong2ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 2).MTPMSC.M210B2C10nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msu_discarded_cong3ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 3).MTPMSC.M210B2C11nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msu_loss_cong1ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 1).MTPMSC.M210B2C12nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msu_loss_cong2ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 2).MTPMSC.M210B2C13nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msu_loss_cong3ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 3).MTPMSC.M210B2C14nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
out_30_peak_cong_start_timeACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPMSC.M210B3C4nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
out_30_peak_load_erlangERLANGFLOATPeak load for outgoing traffic during a 30-minute period.MTPMSC.M210B3C3 / 1000nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
out_5_peak_cong_start_timeACCUMULATIONINT8Start time of the 5-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPMSC.M210B3C8nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
out_5_peak_load_erlangERLANGFLOATPeak load for incoming traffic during a 5-minute period.MTPMSC.M210B3C7 / 1000nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
outgoing_utilisationACCUMULATIONFLOATOutgoing utilisation of the signalling linkif MTPMSC.M210B1C2 < 1 then 100 else (M210B2C1 + 6 * (M210B2C3 * 8)) / ((interval*60) * M210B1C2)nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
retransmitsACCUMULATIONINT8The number of octets retransmitted.MTPMSC.M210B2C5nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sif_sio_receivedACCUMULATIONINT8The number of received SIF and SIO octetsMTPMSC.M210B2C2nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sif_sio_transACCUMULATIONINT8The number of SIF and SIO octets transmitted.MTPMSC.M210B2C1nkmtbh, nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh


Signalling_Link.Nokia.GSM.MSC_Signalling_point_perform_2

Signalling link performance for MSC node

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changebacksACCUMULATIONINT8Automatic changebackSLPNMSC.M209B3C4nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
automatic_changeoversACCUMULATIONINT8Automatic changeoverSLPNMSC.M209B3C3nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
dur_in_service_stateACCUMULATIONINT8Duration of signalling link in the in-service stateSLPNMSC.M209B2C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8Signalling link failure - abnormal FIBR/BSNRSLPNMSC.M209B2C3nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_ali_or_prov_failACCUMULATIONINT8Signalling link alignment or proving failureSLPNMSC.M209B2C7nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_all_reasonsACCUMULATIONINT8Signalling link failures - all reasonsSLPNMSC.M209B2C2nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_exc_del_of_ackACCUMULATIONINT8Caused by excessive delay of acknowledgementSLPNMSC.M209B2C4nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_exc_dur_of_congACCUMULATIONINT8Signalling link failure - excessive duration of congestionSLPNMSC.M209B2C6nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_exc_error_rateACCUMULATIONINT8Signalling link failure - excessive error rateSLPNMSC.M209B2C5nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_failures_m_err_ind_sd_losACCUMULATIONINT8MAA-ERROR indication with Error Type SD lossSLPNMSC.M209B2C8nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
link_restorationsACCUMULATIONINT8Signalling link restorationSLPNMSC.M209B3C5nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
negative_acksACCUMULATIONINT8Number of negative acknowledgements receivedSLPNMSC.M209B3C2nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sign_units_received_in_errorACCUMULATIONINT8Number of signal units received in errorSLPNMSC.M209B3C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh


Signalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2

Signalling link utilisation for MSC node

KPITypeData TypeDescriptionDerivationAdditional Summaries
BIT_RATEINTENSITYINTEGERThe type of the link, TDM=0 or ATM=1.MTPNMSC.M210B1C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
cumulative_duration_level1ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 1).MTPNMSC.M210B2C15nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
cumulative_duration_level2ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 2).MTPNMSC.M210B2C16nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
cumulative_duration_level3ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 3).MTPNMSC.M210B2C17nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
events_res_in_loss_of_msus_l1ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 1).MTPNMSC.M210B2C12nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
events_res_in_loss_of_msus_l2ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 2).MTPNMSC.M210B2C13nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
events_res_in_loss_of_msus_l3ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 3).MTPNMSC.M210B2C14nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
incoming_utilisationACCUMULATIONFLOATIncoming utilisation of the signalling linkif MTPNMSC.M210B1C2 < 1 then 100 else (M210B2C2 + 6 * (M210B2C4 * 8)) / ((interval*60) * M210B1C2)nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_30_peak_traf_in_startedACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedMTPNMSC.M210B3C2nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_30_peak_traf_out_startedACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPNMSC.M210B3C4nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_30_peakload_traffic_inERLANGINT830 minutes peak load in milliErlangs for incoming trafficMTPNMSC.M210B3C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_30_peakload_traffic_outERLANGINT830 minutes peak load in milliErlangs for outgoing trafficMTPNMSC.M210B3C3nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_5_peak_traf_in_startedACCUMULATIONINT8Start time of the 5 minutes freezing period when the peak congestion for incoming traffic was noticed (Measured as minutes from measurement period start time.)MTPNMSC.M210B3C6nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_5_peak_traf_out_startedACCUMULATIONINT8Start time of the 5 minutes freezing period when the peak congestion for outgoing traffic was noticed. (Measured as minutes from measurement period start time.)MTPNMSC.M210B3C8nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_5_peakload_traffic_inERLANGINT85 minutes peak load in milliErlangs for incoming trafficMTPNMSC.M210B3C5nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
min_5_peakload_traffic_outERLANGINT85 minutes peak load in milliErlangs for outgoing trafficMTPNMSC.M210B3C7nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msus_discarded_level1ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 1).MTPNMSC.M210B2C9nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msus_discarded_level2ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 2).MTPNMSC.M210B2C10nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msus_discarded_level3ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 3).MTPNMSC.M210B2C11nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msus_receivedACCUMULATIONINT8The number of message signal units received.MTPNMSC.M210B2C4nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
msus_transmittedACCUMULATIONINT8The number of message signal units transmitted.MTPNMSC.M210B2C3nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
octets_retransmittedACCUMULATIONINT8The number of octets retransmitted.MTPNMSC.M210B2C5nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
outgoing_utilisationACCUMULATIONFLOATOutgoing utilisation of the signalling linkif MTPNMSC.M210B1C2 < 1 then 100 else (M210B2C1 + 6 * (M210B2C3 * 8)) / ((interval*60) * M210B1C2)nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sif_and_sio_octets_receivedACCUMULATIONINT8The number of received SIF and SIO octetsMTPNMSC.M210B2C2nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sif_and_sio_octets_transmittedACCUMULATIONINT8The number of SIF and SIO octets transmitted.MTPNMSC.M210B2C1nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sl_congestion_level1ACCUMULATIONINT8Signalling link congestion (level 1).MTPNMSC.M210B2C6nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sl_congestion_level2ACCUMULATIONINT8Signalling link congestion (level 2).MTPNMSC.M210B2C7nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh
sl_congestion_level3ACCUMULATIONINT8Signalling link congestion (level 3).MTPNMSC.M210B2C8nkslmrxbh, nkslmtxbh, nkslrxbh, nksltxbh


Signalling_Link.Nokia.GSM.SRR_Signalling_Link_Avail_2

Signalling link availability measurements for SRR node

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to local management actionsSLASRR.M208B2C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_inhibit_rem_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to remote management actionsSLASRR.M208B2C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_local_busy_atmACCUMULATIONINT8Duration of local busy (ATM) (2.15 in ITU-T Q.752).SLASRR.M208B2C16nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_local_busyACCUMULATIONINT8Duration of local busy (number of SIBs).SLASRR.M208B2C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_unavail_link_failureACCUMULATIONINT8Duration of signalling link unavailability due to link failureSLASRR.M208B2C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_unavail_local_blockingACCUMULATIONINT8Duration of signalling link unavailability due to local blockingSLASRR.M208B2C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_unavail_rem_proc_outageACCUMULATIONINT8Duration of signalling link unavailability due to remote processor outageSLASRR.M208B2C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_of_unavailACCUMULATIONINT8Duration of signalling link unavailability for any reasonSLASRR.M208B2C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
loc_manag_inhibitACCUMULATIONINT8Local management inhibit.SLASRR.M208B2C12nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
loc_manag_uninhibitedACCUMULATIONINT8Local management uninhibit.SLASRR.M208B2C13nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
local_manual_changeoversACCUMULATIONINT8Local manual changeovers and changeovers due to system recovery actions.SLASRR.M208B2C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
rem_inhibitACCUMULATIONINT8Start of remote inhibition.SLASRR.M208B2C14nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
rem_proc_outage_startACCUMULATIONINT8Start of remote processor outage.SLASRR.M208B2C10nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
rem_proc_outage_stopACCUMULATIONINT8Stop of remote processor outage.SLASRR.M208B2C11nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
rem_uninhibitedACCUMULATIONINT8End of remote inhibition.SLASRR.M208B2C15nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
remote_initiative_changeoversACCUMULATIONINT8Remote initiative changeovers.SLASRR.M208B2C9nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh


Signalling_Link.Nokia.GSM.SRR_Signalling_Link_Availability

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to local management actions (2.5 in ITU-T Q.752) (seconds)SLSRR.M208B2C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_inhibit_rem_manag_actACCUMULATIONINT8Duration of signalling link inhibition due to remote management actions (2.6 in ITU-T Q.752) (seconds)SLSRR.M208B2C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_local_busy_atmACCUMULATIONINT8Duration of local busy (ATM) (2.15 in ITU-T Q.752).SLSRR.M208B2C16nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_local_busyACCUMULATIONINT8Duration of local busy (number of SIBs).(2.15 in ITU-T Q.752)SLSRR.M208B2C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_unavail_link_failureACCUMULATIONINT8Duration of signalling link unavailability due to link failure (2.7 in ITU-T Q.752) (seconds)SLSRR.M208B2C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_unavail_local_blockingACCUMULATIONINT8Duration of signalling link unavailability due to local blocking (2.8 in ITU-T Q.752) (seconds)SLSRR.M208B2C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_unavail_rem_proc_outageACCUMULATIONINT8Duration of signalling link unavailability due to remote processor outage (2.9 in ITU-T Q.752) (seconds)SLSRR.M208B2C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_of_unavailACCUMULATIONINT8Duration of signalling link unavailability for any reason (2.1 in ITU-T Q.752) (seconds)SLSRR.M208B2C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
loc_manag_inhibitACCUMULATIONINT8Local management inhibit (2.13 in ITU-T Q.752)SLSRR.M208B2C12nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
loc_manag_uninhibitedACCUMULATIONINT8Local management uninhibit (2.14 in ITU-T Q.752)SLSRR.M208B2C13nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
local_manual_changeoversACCUMULATIONINT8Local manual changeovers and changeovers due to system recovery actions (2.2 in ITU-T Q.752)SLSRR.M208B2C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
rem_inhibitACCUMULATIONINT8Start of remote inhibition (2.18 in ITU-T Q.752)SLSRR.M208B2C14nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
rem_proc_outage_startACCUMULATIONINT8Start of remote processor outage (2.10 in ITU-T Q.752)SLSRR.M208B2C10nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
rem_proc_outage_stopACCUMULATIONINT8Stop of remote processor outage (2.11 in ITU-T Q.752)SLSRR.M208B2C11nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
rem_uninhibitedACCUMULATIONINT8End of remote inhibition (2.19 in ITU-T Q.752)SLSRR.M208B2C15nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
remote_initiative_changeoversACCUMULATIONINT8Remote initiative changeovers (2.3 in ITU-T Q.752)SLSRR.M208B2C9nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh


Signalling_Link.Nokia.GSM.SRR_Signalling_Link_Performance

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changebacksACCUMULATIONINT8Automatic changeback (1.11 in ITU-T Q.752)SLPSRR.M209B3C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
automatic_changeoversACCUMULATIONINT8Automatic changeover (1.10 in ITU-T Q.752)SLPSRR.M209B3C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
dur_in_service_stateACCUMULATIONINT8Duration of signalling link in the in-service state (1.1 in ITU-T Q.752) (seconds)SLPSRR.M209B2C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8Signalling link failure - abnormal FIBR/BSNR (TDM) (1.3 in ITU-T Q.752, not used if link type = 1) SLPSRR.M209B2C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_ali_or_prov_failACCUMULATIONINT8Signalling link alignment or proving failure (1.7 in ITU-T Q.752)SLPSRR.M209B2C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_all_reasonsACCUMULATIONINT8Signalling link failures - all reasons (1.2 in ITU-T Q.752)SLPSRR.M209B2C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_exc_del_of_ackACCUMULATIONINT8Caused by excessive delay of acknowledgement (TDM)(1.4 in ITU-T Q.752),SLPSRR.M209B2C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_exc_dur_of_congACCUMULATIONINT8Signalling link failure - excessive duration of congestion (1.6 in ITU-T Q.752)SLPSRR.M209B2C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_exc_error_rateACCUMULATIONINT8Signalling link failure - excessive error rate (1.5 in ITU-T Q.752)SLPSRR.M209B2C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_failures_m_err_ind_sd_losACCUMULATIONINT8MAA-ERROR indication with Error Type SD loss (ATM) (1.7 in ITU-T Q.2144, not used if link type = 0)SLPSRR.M209B2C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
link_restorationsACCUMULATIONINT8Signalling link restoration (1.12 in ITU-T Q.752)SLPSRR.M209B3C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
negative_acksACCUMULATIONINT8Number of negative acknowledgements received (TDM) (1.9 in ITU-T Q.752, not used if link is ATM link)SLPSRR.M209B3C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
sign_units_received_in_errorACCUMULATIONINT8Number of signal units received in error (TDM) (1.8 in ITU-T Q.752, not used if link is ATM link)SLPSRR.M209B3C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh


Signalling_Link.Nokia.GSM.SRR_Signalling_Link_Utilisation

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cong1ACCUMULATIONINT8Signalling link congestion (level 1).MTPSRR.M210B2C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
cong2ACCUMULATIONINT8Signalling link congestion (level 2).MTPSRR.M210B2C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
cong3ACCUMULATIONINT8Signalling link congestion (level 3).MTPSRR.M210B2C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
duration_cong1ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 1).MTPSRR.M210B2C9nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
duration_cong2ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 2).MTPSRR.M210B2C10nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
duration_cong3ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 3).MTPSRR.M210B2C11nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
inc_30_peak_cong_start_timeACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedMTPSRR.M210B3C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
inc_30_peak_load_erlangERLANGFLOATPeak load for incoming traffic during a 30-minute period.MTPSRR.M210B3C1 / 1000nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
inc_5_peak_cong_start_timeACCUMULATIONINT8Start time of the 5-minute freezing period when the peak congestion for the incoming traffic was noticedMTPSRR.M210B3C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
incoming_utilisationACCUMULATIONFLOATIncoming utilisation of the signalling linkif MTPSRR.M210B1C2 < 1 then 100 else (M210B2C2 + 6 * (M210B2C4 * 8)) / ((interval*60) * M210B1C2)nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
min_30_peakload_traffic_inERLANGFLOAT30 minutes peak load in milliErlangs for incoming trafficMTPSRR.M210B3C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
min_30_peakload_traffic_outERLANGFLOAT30 minutes peak load in milliErlangs for outgoing trafficMTPSRR.M210B3C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
min_5_peakload_traffic_inERLANGFLOAT5 minutes peak load in milliErlangs for incoming trafficMTPSRR.M210B3C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
min_5_peakload_traffic_outERLANGFLOAT5 minutes peak load in milliErlangs for outgoing trafficMTPSRR.M210B3C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msg_receivedACCUMULATIONINT8The number of message signal units received.MTPSRR.M210B2C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msg_transACCUMULATIONINT8The number of message signal units transmitted.MTPSRR.M210B2C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msu_discarded_cong1ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 1).MTPSRR.M210B2C12nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msu_discarded_cong2ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 2).MTPSRR.M210B2C13nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msu_discarded_cong3ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 3).MTPSRR.M210B2C14nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msu_loss_cong1ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 1).MTPSRR.M210B2C15nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msu_loss_cong2ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 2).MTPSRR.M210B2C16nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
msu_loss_cong3ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 3).MTPSRR.M210B2C17nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
out_30_peak_cong_start_timeACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPSRR.M210B3C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
out_5_peak_cong_start_timeACCUMULATIONINT8Start time of the 5-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPSRR.M210B3C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
outgoing_utilisationACCUMULATIONFLOATOutgoing utilisation of the signalling linkif MTPSRR.M210B1C2 < 1 then 100 else (M210B2C1 + 6 * (M210B2C3 * 8)) / ((interval*60) * M210B1C2)nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
retransmitsACCUMULATIONINT8The number of octets retransmitted.MTPSRR.M210B2C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
sif_sio_receivedACCUMULATIONINT8The number of received SIF and SIO octetsMTPSRR.M210B2C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh
sif_sio_transACCUMULATIONINT8The number of SIF and SIO octets transmitted.MTPSRR.M210B2C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh, nksrrotbh


Signalling_Link.Nokia.GSM.SRR_Signalling_point_perform_2

Signalling link performance for SRR node

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changebacksACCUMULATIONINT8Automatic changebackSLPNSRR.M209B3C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
automatic_changeoversACCUMULATIONINT8Automatic changeoverSLPNSRR.M209B3C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
dur_in_service_stateACCUMULATIONINT8Duration of signalling link in the in-service stateSLPNSRR.M209B2C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8Signalling link failure - abnormal FIBR/BSNRSLPNSRR.M209B2C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_ali_or_prov_failACCUMULATIONINT8Signalling link alignment or proving failureSLPNSRR.M209B2C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_all_reasonsACCUMULATIONINT8Signalling link failures - all reasonsSLPNSRR.M209B2C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_exc_del_of_ackACCUMULATIONINT8Caused by excessive delay of acknowledgementSLPNSRR.M209B2C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_exc_dur_of_congACCUMULATIONINT8Signalling link failure - excessive duration of congestionSLPNSRR.M209B2C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_exc_error_rateACCUMULATIONINT8Signalling link failure - excessive error rateSLPNSRR.M209B2C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_failures_m_err_ind_sd_losACCUMULATIONINT8MAA-ERROR indication with Error Type SD lossSLPNSRR.M209B2C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
link_restorationsACCUMULATIONINT8Signalling link restorationSLPNSRR.M209B3C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
negative_acksACCUMULATIONINT8Number of negative acknowledgements receivedSLPNSRR.M209B3C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
sign_units_received_in_errorACCUMULATIONINT8Number of signal units received in errorSLPNSRR.M209B3C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh


Signalling_Link.Nokia.GSM.SRR_Signalling_Point_Util_2

Signalling link utilisation for SRR node

KPITypeData TypeDescriptionDerivationAdditional Summaries
BIT_RATEINTENSITYINTEGERThe type of the link, TDM=0 or ATM=1.MTPNSRR.M210B1C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
cumulative_duration_level1ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 1).MTPNSRR.M210B2C15nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
cumulative_duration_level2ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 2).MTPNSRR.M210B2C16nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
cumulative_duration_level3ACCUMULATIONINT8Cumulative duration of signalling link congestion (level 3).MTPNSRR.M210B2C17nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
events_res_in_loss_of_msus_l1ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 1).MTPNSRR.M210B2C12nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
events_res_in_loss_of_msus_l2ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 2).MTPNSRR.M210B2C13nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
events_res_in_loss_of_msus_l3ACCUMULATIONINT8The number of congestion events resulting in loss of MSUs (level 3).MTPNSRR.M210B2C14nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
incoming_utilisationACCUMULATIONFLOATIncoming utilisation of the signalling linkif MTPNSRR.M210B1C2 < 1 then 100 else (M210B2C2 + 6 * (M210B2C4 * 8)) / ((interval*60) * M210B1C2)nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_30_peak_traf_in_startedACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedMTPNSRR.M210B3C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_30_peak_traf_out_startedACCUMULATIONINT8Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedMTPNSRR.M210B3C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_30_peakload_traffic_inERLANGINT830 minutes peak load in milliErlangs for incoming trafficMTPNSRR.M210B3C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_30_peakload_traffic_outERLANGINT830 minutes peak load in milliErlangs for outgoing trafficMTPNSRR.M210B3C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_5_peak_traf_in_startedACCUMULATIONINT8Start time of the 5 minutes freezing period when the peak congestion for incoming traffic was noticed (Measured as minutes from measurement period start time.)MTPNSRR.M210B3C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_5_peak_traf_out_startedACCUMULATIONINT8Start time of the 5 minutes freezing period when the peak congestion for outgoing traffic was noticed. (Measured as minutes from measurement period start time.)MTPNSRR.M210B3C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_5_peakload_traffic_inERLANGINT85 minutes peak load in milliErlangs for incoming trafficMTPNSRR.M210B3C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
min_5_peakload_traffic_outERLANGINT85 minutes peak load in milliErlangs for outgoing trafficMTPNSRR.M210B3C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
msus_discarded_level1ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 1).MTPNSRR.M210B2C9nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
msus_discarded_level2ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 2).MTPNSRR.M210B2C10nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
msus_discarded_level3ACCUMULATIONINT8The number of message signal units (MSU) discarded due to signalling link congestion (level 3).MTPNSRR.M210B2C11nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
msus_receivedACCUMULATIONINT8The number of message signal units received.MTPNSRR.M210B2C4nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
msus_transmittedACCUMULATIONINT8The number of message signal units transmitted.MTPNSRR.M210B2C3nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
octets_retransmittedACCUMULATIONINT8The number of octets retransmitted.MTPNSRR.M210B2C5nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
outgoing_utilisationACCUMULATIONFLOATOutgoing utilisation of the signalling linkif MTPNSRR.M210B1C2 < 1 then 100 else (M210B2C1 + 6 * (M210B2C3 * 8)) / ((interval*60) * M210B1C2)nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
sif_and_sio_octets_receivedACCUMULATIONINT8The number of received SIF and SIO octetsMTPNSRR.M210B2C2nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
sif_and_sio_octets_transmittedACCUMULATIONINT8The number of SIF and SIO octets transmitted.MTPNSRR.M210B2C1nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
sl_congestion_level1ACCUMULATIONINT8Signalling link congestion (level 1).MTPNSRR.M210B2C6nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
sl_congestion_level2ACCUMULATIONINT8Signalling link congestion (level 2).MTPNSRR.M210B2C7nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh
sl_congestion_level3ACCUMULATIONINT8Signalling link congestion (level 3).MTPNSRR.M210B2C8nkslsrrxbh, nkslsrtxbh, nkslsrxbh, nkslstxbh


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.Nokia.GSM.HLR_Linkset_and_Routeset_Availability

HLR Linkset and routeset availability data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
initiation_of_broadcast_tfaACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restorationAVANHLR.M212B2C5 
initiation_of_broadcast_tfpACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failureAVANHLR.M212B2C4 
sl_set_duration_of_unaACCUMULATIONINT8Duration of unavailability of signalling link setAVANHLR.M212B2C3 
sl_set_start_failureINTENSITYINT8Start of signalling link set failureAVANHLR.M212B2C1 
sl_set_stop_failureINTENSITYINT8Stop of signalling link set failureAVANHLR.M212B2C2 
sr_set_una_due_to_tfp_recACCUMULATIONINT8Unavailability of signalling route set due to transfer prohibited message receivedAVANHLR.M212B2C6 
sr_set_una_dura_due_to_tfp_recACCUMULATIONINT8Duration of unavailability of signalling route set due to transfer prohibited message receivedAVANHLR.M212B2C8 
sr_set_una_dura_to_given_destACCUMULATIONINT8Duration of unavailability of signalling route setAVANHLR.M212B2C9 
sr_set_una_to_given_destACCUMULATIONINT8Unavailability of signalling route setAVANHLR.M212B2C7 


Signalling_LinkSet.Nokia.GSM.HLR_Signalling_LinkSet_Availability

HLR signalling linkset availability data

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of signalling link inhibition due to local management actionsobsolete.obsolete 
dur_of_inhibit_rem_manag_actACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of signalling link inhibition due to remote management actionsobsolete.obsolete 
dur_of_local_busy_atmACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of local busy (ATM) (2.15 in ITU-T Q.752).obsolete.obsolete 
dur_of_local_busyACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of local busy (number of SIBs).obsolete.obsolete 
dur_of_unavail_link_failureACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of signalling link unavailability due to link failureobsolete.obsolete 
dur_of_unavail_local_blockingACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of signalling link unavailability due to local blockingobsolete.obsolete 
dur_of_unavail_rem_proc_outageACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of signalling link unavailability due to remote processor outageobsolete.obsolete 
dur_of_unavailACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Duration of signalling link unavailability for any reasonobsolete.obsolete 
loc_manag_inhibitACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Local management inhibit.obsolete.obsolete 
loc_manag_uninhibitedACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Local management uninhibit.obsolete.obsolete 
local_manual_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Local manual changeovers and changeovers due to system recovery actions.obsolete.obsolete 
rem_inhibitACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Start of remote inhibition.obsolete.obsolete 
rem_proc_outage_startACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Start of remote processor outage.obsolete.obsolete 
rem_proc_outage_stopACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Stop of remote processor outage.obsolete.obsolete 
rem_uninhibitedACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) End of remote inhibition.obsolete.obsolete 
remote_initiative_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLAHLR block now parked under Signalling_Link object) Remote initiative changeovers.obsolete.obsolete 


Signalling_LinkSet.Nokia.GSM.MSC_Linkset_and_Routeset_Availability

MSC linkset and routeset availability data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
initiation_of_broadcast_tfaACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restorationAVANMSC.M212B2C5 
initiation_of_broadcast_tfpACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failureAVANMSC.M212B2C4 
sl_set_duration_of_unaACCUMULATIONINT8Duration of unavailability of signalling link setAVANMSC.M212B2C3 
sl_set_start_failureINTENSITYINT8Start of signalling link set failureAVANMSC.M212B2C1 
sl_set_stop_failureINTENSITYINT8Stop of signalling link set failureAVANMSC.M212B2C2 
sr_set_una_due_to_tfp_recACCUMULATIONINT8Unavailability of signalling route set due to transfer prohibited message receivedAVANMSC.M212B2C6 
sr_set_una_dura_due_to_tfp_recACCUMULATIONINT8Duration of unavailability of signalling route set due to transfer prohibited message receivedAVANMSC.M212B2C8 
sr_set_una_dura_to_given_destACCUMULATIONINT8Duration of unavailability of signalling route setAVANMSC.M212B2C9 
sr_set_una_to_given_destACCUMULATIONINT8Unavailability of signalling route setAVANMSC.M212B2C7 


Signalling_LinkSet.Nokia.GSM.MSC_Signalling_LinkSet_Availability

MSC signalling linkset availability data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of signalling link inhibition due to local management actionsobsolete.obsolete 
dur_of_inhibit_rem_manag_actACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of signalling link inhibition due to remote management actionsobsolete.obsolete 
dur_of_local_busy_atmACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of local busy (ATM) (2.15 in ITU-T Q.752).obsolete.obsolete 
dur_of_local_busyACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of local busy (number of SIBs).obsolete.obsolete 
dur_of_unavail_link_failureACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of signalling link unavailability due to link failureobsolete.obsolete 
dur_of_unavail_local_blockingACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of signalling link unavailability due to local blockingobsolete.obsolete 
dur_of_unavail_rem_proc_outageACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of signalling link unavailability due to remote processor outageobsolete.obsolete 
dur_of_unavailACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Duration of signalling link unavailability for any reasonobsolete.obsolete 
loc_manag_inhibitACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Local management inhibit.obsolete.obsolete 
loc_manag_uninhibitedACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Local management uninhibit.obsolete.obsolete 
local_manual_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Local manual changeovers and changeovers due to system recovery actions.obsolete.obsolete 
rem_inhibitACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Start of remote inhibition.obsolete.obsolete 
rem_proc_outage_startACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Start of remote processor outage.obsolete.obsolete 
rem_proc_outage_stopACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Stop of remote processor outage.obsolete.obsolete 
rem_uninhibitedACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) End of remote inhibition.obsolete.obsolete 
remote_initiative_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLAMSC block now parked under Signalling_Link object) Remote initiative changeovers.obsolete.obsolete 


Signalling_LinkSet.Nokia.GSM.SRR_Linkset_and_Routeset_Availability

SRR linkset and routeset availability data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
initiation_of_broadcast_tfaACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restorationAVANSRR.M212B2C5 
initiation_of_broadcast_tfpACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failureAVANSRR.M212B2C4 
sl_set_duration_of_unaACCUMULATIONINT8Duration of unavailability of signalling link setAVANSRR.M212B2C3 
sl_set_start_failureINTENSITYINT8Start of signalling link set failureAVANSRR.M212B2C1 
sl_set_stop_failureINTENSITYINT8Stop of signalling link set failureAVANSRR.M212B2C2 
sr_set_una_due_to_tfp_recACCUMULATIONINT8Unavailability of signalling route set due to transfer prohibited message receivedAVANSRR.M212B2C6 
sr_set_una_dura_due_to_tfp_recACCUMULATIONINT8Duration of unavailability of signalling route set due to transfer prohibited message receivedAVANSRR.M212B2C8 
sr_set_una_dura_to_given_destACCUMULATIONINT8Duration of unavailability of signalling route setAVANSRR.M212B2C9 
sr_set_una_to_given_destACCUMULATIONINT8Unavailability of signalling route setAVANSRR.M212B2C7 


Signalling_LinkSet.Nokia.GSM.SRR_Signalling_LinkSet_Availability

SRR signalling linkset availability data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
dur_of_inhibit_loc_manag_actACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of signalling link inhibition due to local management actionsobsolete.obsolete 
dur_of_inhibit_rem_manag_actACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of signalling link inhibition due to remote management actionsobsolete.obsolete 
dur_of_local_busy_atmACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of local busy (ATM) (2.15 in ITU-T Q.752).obsolete.obsolete 
dur_of_local_busyACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of local busy (number of SIBs).obsolete.obsolete 
dur_of_unavail_link_failureACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of signalling link unavailability due to link failureobsolete.obsolete 
dur_of_unavail_local_blockingACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of signalling link unavailability due to local blockingobsolete.obsolete 
dur_of_unavail_rem_proc_outageACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of signalling link unavailability due to remote processor outageobsolete.obsolete 
dur_of_unavailACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Duration of signalling link unavailability for any reasonobsolete.obsolete 
loc_manag_inhibitACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Local management inhibit.obsolete.obsolete 
loc_manag_uninhibitedACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Local management uninhibit.obsolete.obsolete 
local_manual_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Local manual changeovers and changeovers due to system recovery actions.obsolete.obsolete 
rem_inhibitACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Start of remote inhibition.obsolete.obsolete 
rem_proc_outage_startACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Start of remote processor outage.obsolete.obsolete 
rem_proc_outage_stopACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Stop of remote processor outage.obsolete.obsolete 
rem_uninhibitedACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) End of remote inhibition.obsolete.obsolete 
remote_initiative_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLASRR block now parked under Signalling_Link object) Remote initiative changeovers.obsolete.obsolete 


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.Nokia.GSM.HLR_Authentication_Count

Authentication count measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
number_of_quintetsACCUMULATIONINT8The number of transferred authentication quintets.ACHSPC.M87B3C24 
number_of_syncreqACCUMULATIONINT8The number of synchronization requests which can be sent when the mobile rejects the authentication because the sequence number is out of range.ACHSPC.M87B3C22 
number_of_unknownsubscACCUMULATIONINT8The number of unknown subscribers whose data was not found in the ACACHSPC.M87B3C23 
numberofansweredACCUMULATIONINT8The number of answers received to the VLR/SGSN authentication vector requests. These answers contain authentication vectors. If the number of requests is larger than the number of answers, the subscriber has not been created in the AC and the answer to the authentication vector request does not contain authentication vector. It is possible that the data on the subscribers location in the ACUs has not yet been updated after the system has been restarted.ACHSPC.M87B3C4 
numberofrequestsACCUMULATIONINT8The number of authentication vector (triplets and quintets) requests. This field also contains the synchronization requests.ACHSPC.M87B3C3 
numberoftripletsACCUMULATIONINT8the number of transferred authentication triplets.ACHSPC.M87B3C5 


Signalling_Point.Nokia.GSM.HLR_Linkset_and_Routeset_Availability

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
duration_link_set_unavailACCUMULATIONINT8Duration of unavailability of signalling link set AVAHLR.M212B2C3 
duration_route_unavailACCUMULATIONINT8Duration of unavailability of signalling route transfer prohibited message receivedAVAHLR.M212B2C7 
initiation_of_broadcast_tfaACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restoration.AVAHLR.M212B2C5 
initiation_of_broadcast_tfpACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failure.AVAHLR.M212B2C4 
sr_set_una_due_to_tfp_recACCUMULATIONINT8Unavailability of signalling route set due to transfer prohibited message receivedAVAHLR.M212B2C6 
sr_set_una_dura_due_to_tfp_recACCUMULATIONINT8Duration of unavailability of signalling route set due to transfer prohibited message receivedAVAHLR.M212B2C8 
sr_set_una_dura_to_given_destACCUMULATIONINT8Duration of unavailability of signalling routesetAVAHLR.M212B2C9 
start_time_link_set_failACCUMULATIONINT8Start of signalling link set failure.AVAHLR.M212B2C1 
stop_time_link_set_failACCUMULATIONINT8Stop of signalling link set failure.AVAHLR.M212B2C2 


Signalling_Point.Nokia.GSM.HLR_SCCP_Signalling_Point_Errors

This section describes the counters of M216. Specifically relating to Errors. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_release_complete_class2ACCUMULATIONINT8Failure of release complete supervision, protocol class 2SCCPHLR.M216B3C9 
err_release_complete_class3ACCUMULATIONINT8Failure of release complete supervision, protocol class 3SCCPHLR.M216B3C10 
gt_translationACCUMULATIONINT8Routing error - no translation of a specific GTSCCPHLR.M216B2C6 
gt_unknownACCUMULATIONINT8Routing error - no translation of unknown GT typeSCCPHLR.M216B2C5 
gt1_failACCUMULATIONINT8Routing error - no translation of GT type 1SCCPHLR.M216B2C1 
gt2_failACCUMULATIONINT8Routing error - no translation of GT type 2SCCPHLR.M216B2C2 
gt3_failACCUMULATIONINT8Routing error - no translation of GT type 3SCCPHLR.M216B2C3 
gt4_failACCUMULATIONINT8Routing error - no translation of GT type 4SCCPHLR.M216B2C4 
net_failACCUMULATIONINT8Routing error - due to a failure in the networkSCCPHLR.M216B2C7 
net_overloadACCUMULATIONINT8Routing error - due to network overloadSCCPHLR.M216B2C8 
provider_connection_releaseACCUMULATIONINT8Provider initiated release of a connectionSCCPHLR.M216B3C14 
provider_connection_resetACCUMULATIONINT8Provider initiated reset of a connectionSCCPHLR.M216B3C13 
subsystem_failACCUMULATIONINT8Routing error - due to a failure in the subsystemSCCPHLR.M216B2C9 
subsystem_overloadACCUMULATIONINT8Routing error - due to subsystem overloadSCCPHLR.M216B2C10 
syntax_errorACCUMULATIONINT8Observed syntax errorsSCCPHLR.M216B2C13 
timer_expiry_class2ACCUMULATIONINT8Timer T(iar) expiry, protocol class 2SCCPHLR.M216B3C11 
timer_expiry_class3ACCUMULATIONINT8Timer T(iar) expiry, protocol class 3SCCPHLR.M216B3C12 
unequipped_userACCUMULATIONINT8Routing error - unequipped userSCCPHLR.M216B2C11 
unknown_reasonACCUMULATIONINT8Routing error - unknown userSCCPHLR.M216B2C12 


Signalling_Point.Nokia.GSM.HLR_SCCP_Signalling_Point_Messages

This section describes the counters of M216. Specifically relating to Messages. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
cr_receivedACCUMULATIONINT8CR messages received from the MTP plus ISDN-UP embedded CRsSCCPHLR.M216B3C2 
cr_transACCUMULATIONINT8CR messages sent to the MTP plus ISDN-UP embedded CRsSCCPHLR.M216B3C1 
cref_receivedACCUMULATIONINT8CREF messages received from the MTPSCCPHLR.M216B3C4 
cref_transACCUMULATIONINT8CREF messages sent to the MTPSCCPHLR.M216B3C3 
err_receivedACCUMULATIONINT8ERR messages received from the MTPSCCPHLR.M216B3C8 
err_transACCUMULATIONINT8ERR messages sent to the MTPSCCPHLR.M216B3C7 
ludt_receivedACCUMULATIONINT8LUDT messages receivedSCCPHLR.M216B2C23 
ludt_transACCUMULATIONINT8LUDT messages sentSCCPHLR.M216B2C22 
ludts_receivedACCUMULATIONINT8LUDTS messages receivedSCCPHLR.M216B2C25 
ludts_transACCUMULATIONINT8LUDTS messages sentSCCPHLR.M216B2C24 
rsr_receivedACCUMULATIONINT8RSR messages received from the MTPSCCPHLR.M216B3C6 
rsr_transACCUMULATIONINT8RSR messages sent to the MTPSCCPHLR.M216B3C5 
udt_receivedACCUMULATIONINT8UDT messages receivedSCCPHLR.M216B2C15 
udt_transACCUMULATIONINT8UDT messages sentSCCPHLR.M216B2C14 
udts_receivedACCUMULATIONINT8UDTS messages receivedSCCPHLR.M216B2C17 
udts_transACCUMULATIONINT8UDTS messages sentSCCPHLR.M216B2C16 
xudt_receivedACCUMULATIONINT8XUDT messages receivedSCCPHLR.M216B2C19 
xudt_transACCUMULATIONINT8XUDT messages sentSCCPHLR.M216B2C18 
xudts_receivedACCUMULATIONINT8XUDTS messages receivedSCCPHLR.M216B2C21 
xudts_transACCUMULATIONINT8XUDTS messages sentSCCPHLR.M216B2C20 


Signalling_Point.Nokia.GSM.HLR_SCCP_Signalling_Point_Subsystem

This section describes the counters of M216. N.B. There is a secondary key of signalling_network and also subsystem

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
allowed_receivedACCUMULATIONINT8Subsystem allowed messages receivedSCCHLR.M216B4C3 
cong_receivedACCUMULATIONINT8SCCP/subsystem congested message receivedSCCHLR.M216B4C1 
prohibited_receivedACCUMULATIONINT8Subsystem prohibited messages receivedSCCHLR.M216B4C2 


Signalling_Point.Nokia.GSM.HLR_Signalling_point_performance

HLR signalling point performance data

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Automatic changeoverobsolete.obsolete 
dur_in_service_stateACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Duration of signalling link in the in-service stateobsolete.obsolete 
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Signalling link failure - abnormal FIBR/BSNRobsolete.obsolete 
link_failures_ali_or_prov_failACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Signalling link alignment or proving failureobsolete.obsolete 
link_failures_all_reasonsACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Signalling link failures - all reasonsobsolete.obsolete 
link_failures_exc_del_of_ackACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Caused by excessive delay of acknowledgementobsolete.obsolete 
link_failures_exc_dur_of_congACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Signalling link failure - excessive duration of congestionobsolete.obsolete 
link_failures_exc_error_rateACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Signalling link failure - excessive error rateobsolete.obsolete 
link_failures_m_err_ind_sd_losACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) MAA-ERROR indication with Error Type SD lossobsolete.obsolete 
link_restorationsACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Signalling link restorationobsolete.obsolete 
negative_acksACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Number of negative acknowledgements receivedobsolete.obsolete 
sign_units_received_in_errorACCUMULATIONINT8(Obsolete in M13.5, SLPNHLR block now parked under Signalling_Link object) Number of signal units received in errorobsolete.obsolete 


Signalling_Point.Nokia.GSM.HLR_Signalling_Point_Status

This measurement contains measurement data of one or more MTP signalling links. NB: there is a secondary key of signalling_network_id

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
adjacent_inaccessibleACCUMULATIONINT8Adjacent signalling point inaccessible.STAHLR.M211B2C2 
duration_adjacentACCUMULATIONINT8Duration of inaccessibility of adjacent signalling point (seconds, minutes, hours, days).STAHLR.M211B2C1 
msgACCUMULATIONINT8The number of transfer controlled messages received.STAHLR.M211B2C3 
msu_discarded_routing_recACCUMULATIONINT8The number of message signal units (MSU) discarded due to routing data error (received).STAHLR.M211B2C5 
msu_discarded_routing_transACCUMULATIONINT8The number of message signal units (MSU) discarded due to routing data error (transmitted).STAHLR.M211B2C4 
msu_stp_opcACCUMULATIONINT8Unauthorised stp msu count for inhibited opc.STAHLR.M211B2C7 
msu_stp_spcACCUMULATIONINT8Unauthorised stp msu count for inhibited dpc.STAHLR.M211B2C6 
msu_stp_stpACCUMULATIONINT8Unauthorised stp msu count for inhibited stp.STAHLR.M211B2C8 
msu_user_part_recACCUMULATIONINT8User Part unavailable MSU received.STAHLR.M211B2C10 
msu_user_part_transACCUMULATIONINT8User Part unavailable MSU transmitted.STAHLR.M211B2C9 


Signalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic_Matrix

This measurement contains measurement data of one or more signalling points.N.B. There is a secondary key of SIO, origination_point and destination_point

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, Destination_Point (destination_point_id) , Originating_Point (originating_point_id) and SIO (sio_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
msuACCUMULATIONINT8The number of MSUs handled with given OPC, DPC, SIOMTXHLR.M215B2C2 
sif_sioACCUMULATIONINT8The number of SIF and SIO octets handled with given OPC, DPC, SIOMTXHLR.M215B2C1 


Signalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic_STP

This section describes the key columns and counters of M213. N.B. There is a secondary key of signalling_transfer_point

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Transfer_Point (signalling_transfer_point_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_dpcACCUMULATIONINT8The number of transmitted SIF and SIO octets with a given DPC.SIGSHLR.M213B3C1 


Signalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic_User

This measurement contains measurement data of one or more MTP user parts.N.B. There is a secondary key of SIO

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and SIO (sio_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8(Obsolete in M13.5, UTRAHLR block now parked under HLR object) The number of SIF and SIO received with the given SIO.obsolete.obsolete 
sif_sio_transACCUMULATIONINT8(Obsolete in M13.5, UTRAHLR block now parked under HLR object) The number of SIF and SIO transmitted with the given SIO.obsolete.obsolete 


Signalling_Point.Nokia.GSM.HLR_Signalling_Point_Traffic

This measurement contains measurement data from one or more MTP signalling points

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8The number of received SIF and SIO octets with a given signalling pointSIGHLR.M213B2C1 
sif_sio_transACCUMULATIONINT8The total number of transmitted SIF and SIO octets.SIGHLR.M213B2C2 


Signalling_Point.Nokia.GSM.HLR_Signalling_Point_Utilisation

HLR Signalling point utilisation data

KPITypeData TypeDescriptionDerivationAdditional Summaries
cumulative_duration_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 1).obsolete.obsolete 
cumulative_duration_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 2).obsolete.obsolete 
cumulative_duration_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 3).obsolete.obsolete 
events_res_in_loss_of_msus_l1ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 1).obsolete.obsolete 
events_res_in_loss_of_msus_l2ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 2).obsolete.obsolete 
events_res_in_loss_of_msus_l3ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 3).obsolete.obsolete 
min_30_peak_traf_in_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedobsolete.obsolete 
min_30_peak_traf_out_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedobsolete.obsolete 
min_30_peakload_traffic_inERLANGINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) 30 minutes peak load in milliErlangs for incoming trafficobsolete.obsolete 
min_30_peakload_traffic_outERLANGINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) 30 minutes peak load in milliErlangs for outgoing trafficobsolete.obsolete 
min_5_peak_traf_in_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Start time of the 5 minutes freezing period when the peak congestion for incoming traffic was noticed (Measured as minutes from measurement period start time.)obsolete.obsolete 
min_5_peak_traf_out_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Start time of the 5 minutes freezing period when the peak congestion for outgoing traffic was noticed. (Measured as minutes from measurement period start time.)obsolete.obsolete 
min_5_peakload_traffic_inERLANGINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) 5 minutes peak load in milliErlangs for incoming trafficobsolete.obsolete 
min_5_peakload_traffic_outERLANGINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) 5 minutes peak load in milliErlangs for outgoing trafficobsolete.obsolete 
msus_discarded_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 1).obsolete.obsolete 
msus_discarded_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 2).obsolete.obsolete 
msus_discarded_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 3).obsolete.obsolete 
msus_receivedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of message signal units received.obsolete.obsolete 
msus_transmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of message signal units transmitted.obsolete.obsolete 
octets_retransmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of octets retransmitted.obsolete.obsolete 
sif_and_sio_octets_receivedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of received SIF and SIO octetsobsolete.obsolete 
sif_and_sio_octets_transmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) The number of SIF and SIO octets transmitted.obsolete.obsolete 
sl_congestion_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Signalling link congestion (level 1).obsolete.obsolete 
sl_congestion_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Signalling link congestion (level 2).obsolete.obsolete 
sl_congestion_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNHLR block now parked under Signalling_Link object) Signalling link congestion (level 3).obsolete.obsolete 


Signalling_Point.Nokia.GSM.MSC_Authentication_Count

Authentication count measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
nbr_quintetACCUMULATIONINT8The number of quintets.ACVSPC.M86B3C22 
numberofansweredACCUMULATIONINT8Number of successful answers received to the VLR authentication vector requestsACVSPC.M86B3C4 
numberofnotansweredACCUMULATIONINT8Number of not answered authentication vector requests.ACVSPC.M86B3C21 
numberofrequestsACCUMULATIONINT8Number of authentication vector requests that were sent by the VLRs. The REQUEST contains the SYNCHRONISATION REQUEST.ACVSPC.M86B3C3 
numberofsyncreqACCUMULATIONINT8The number of synchronisation request which can be sent when the mobile rejects the authentication because the sequence number is out of range.ACVSPC.M86B3C20 
numberoftripletsINTENSITYINTEGERNumber of transferred authentication triplets.ACVSPC.M86B3C6 
numberofunknownsubscINTENSITYINTEGERNumber of subscribers whose data cannot be found in the AUC of the HLR.ACVSPC.M86B3C5 
nweishlrifvalueis_1ACCUMULATIONINT8The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is HLR, which sent the authentication vector. In ASCII report appears HLR in NWE column.ACVSPC.M86B5C1 
nweisplmnifvalueis_1ACCUMULATIONINT8The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is PLMN, which sent the authentication vector. In this case the HLR address of the subscriber is unknown and the VLR calculates the HLR address from IMSI. In ASCII report appears PLMN in NWE column.ACVSPC.M86B5C3 
nweisvlrifvalueis_1ACCUMULATIONINT8The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is VLR, which sent the authentication vector. In ASCII report appears VLR in NWE column and the vectors came from the previous VLR after location update.ACVSPC.M86B5C2 


Signalling_Point.Nokia.GSM.MSC_Linkset_and_Routeset_Availability

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
duration_link_set_unavailACCUMULATIONINT8Duration of unavailability of signalling link set AVAMSC.M212B2C1nkmtbh
duration_route_unavailACCUMULATIONINT8Duration of unavailability of signalling route transfer prohibited message receivedAVAMSC.M212B2C7nkmtbh
initiation_of_broadcast_tfaACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restoration.AVAMSC.M212B2C5nkmtbh
initiation_of_broadcast_tfpACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failureAVAMSC.M212B2C4nkmtbh
sr_set_una_due_to_tfp_recACCUMULATIONINT8Unavailability of signalling route set due to transfer prohibited message received (4.7 in ITU-T Q.752)AVAMSC.M212B2C6nkmtbh
start_time_link_set_failINTENSITYINTEGERStart of signalling link set failure.AVAMSC.M212B2C8nkmtbh
stop_time_link_set_failINTENSITYINTEGERStop of signalling link set failure.AVAMSC.M212B2C9nkmtbh
transfer_block_link_failACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failure.AVAMSC.M212B2C2nkmtbh
transfer_ok_link_upACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restoration.AVAMSC.M212B2C3nkmtbh


Signalling_Point.Nokia.GSM.MSC_SCCP_Signalling_Point_Errors

This section describes the counters of M216 with relation to errors. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (SNET_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_release_complete_class2ACCUMULATIONINT8Failure of release complete supervision, protocol class 2SCCPMSC.M216B3C9nkmtbh
err_release_complete_class3ACCUMULATIONINT8Failure of release complete supervision, protocol class 3SCCPMSC.M216B3C10nkmtbh
gt_translationACCUMULATIONINT8Routing error - no translation of a specific GTSCCPMSC.M216B2C6nkmtbh
gt_unknownACCUMULATIONINT8Routing error - no translation of unknown GT typeSCCPMSC.M216B2C5nkmtbh
gt1_failACCUMULATIONINT8Routing error - no translation of GT type 1SCCPMSC.M216B2C1nkmtbh
gt2_failACCUMULATIONINT8Routing error - no translation of GT type 2SCCPMSC.M216B2C2nkmtbh
gt3_failACCUMULATIONINT8Routing error - no translation of GT type 3SCCPMSC.M216B2C3nkmtbh
gt4_failACCUMULATIONINT8Routing error - no translation of GT type 4SCCPMSC.M216B2C4nkmtbh
net_failACCUMULATIONINT8Routing error - due to a failure in the networkSCCPMSC.M216B2C7nkmtbh
net_overloadACCUMULATIONINT8Routing error - due to network overloadSCCPMSC.M216B2C8nkmtbh
provider_connection_releaseACCUMULATIONINT8Provider initiated release of a connectionSCCPMSC.M216B3C14nkmtbh
provider_connection_resetACCUMULATIONINT8Provider initiated reset of a connectionSCCPMSC.M216B3C13nkmtbh
routing_failure_ss_congestionACCUMULATIONINT8Routing error - due to subsystem overloadSCCPMSC.M216B2C10nkmtbh
subsystem_failACCUMULATIONINT8Routing error - due to a failure in the subsystemSCCPMSC.M216B2C9nkmtbh
subsystem_overloadACCUMULATIONINT8Routing error - due to subsystem overloadSCCPMSC.M216B2C8nkmtbh
syntax_errorACCUMULATIONINT8Observed syntax errorsSCCPMSC.M216B2C13nkmtbh
timer_expiry_class2ACCUMULATIONINT8Timer T(iar) expiry, protocol class 2SCCPMSC.M216B3C11nkmtbh
timer_expiry_class3ACCUMULATIONINT8Timer T(iar) expiry, protocol class 3SCCPMSC.M216B3C12nkmtbh
unequipped_userACCUMULATIONINT8Routing error - unequipped userSCCPMSC.M216B2C11nkmtbh
unknown_reasonACCUMULATIONINT8Routing error - unknown userSCCPMSC.M216B2C12nkmtbh


Signalling_Point.Nokia.GSM.MSC_SCCP_Signalling_Point_Messages

This section describes the counters of M216 with relation to messages. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (SNET_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
cr_receivedACCUMULATIONINT8CR messages received from the MTP plus ISDN-UP embedded CRsSCCPMSC.M216B3C2nkmtbh
cr_transACCUMULATIONINT8CR messages sent to the MTP plus ISDN-UP embedded CRsSCCPMSC.M216B3C1nkmtbh
cref_receivedACCUMULATIONINT8CREF messages received from the MTPSCCPMSC.M216B3C4nkmtbh
cref_transACCUMULATIONINT8CREF messages sent to the MTPSCCPMSC.M216B3C3nkmtbh
err_receivedACCUMULATIONINT8ERR messages received from the MTPSCCPMSC.M216B3C8nkmtbh
err_transACCUMULATIONINT8ERR messages sent to the MTPSCCPMSC.M216B3C7nkmtbh
ludt_receivedACCUMULATIONINT8LUDT messages receivedSCCPMSC.M216B2C23nkmtbh
ludt_transACCUMULATIONINT8LUDT messages sentSCCPMSC.M216B2C22nkmtbh
ludts_receivedACCUMULATIONINT8LUDTS messages receivedSCCPMSC.M216B2C25nkmtbh
ludts_transACCUMULATIONINT8LUDTS messages sentSCCPMSC.M216B2C24nkmtbh
rsr_receivedACCUMULATIONINT8RSR messages received from the MTPSCCPMSC.M216B3C6nkmtbh
rsr_transACCUMULATIONINT8RSR messages sent to the MTPSCCPMSC.M216B3C5nkmtbh
udt_receivedACCUMULATIONINT8UDT messages receivedSCCPMSC.M216B2C15nkmtbh
udt_transACCUMULATIONINT8UDT messages sentSCCPMSC.M216B2C14nkmtbh
udts_receivedACCUMULATIONINT8UDTS messages receivedSCCPMSC.M216B2C17nkmtbh
udts_transACCUMULATIONINT8UDTS messages sentSCCPMSC.M216B2C16nkmtbh
xudt_receivedACCUMULATIONINT8XUDT messages receivedSCCPMSC.M216B2C19nkmtbh
xudt_transACCUMULATIONINT8XUDT messages sentSCCPMSC.M216B2C18nkmtbh
xudts_receivedACCUMULATIONINT8XUDTS messages receivedSCCPMSC.M216B2C21nkmtbh
xudts_transACCUMULATIONINT8XUDTS messages sentSCCPMSC.M216B2C20nkmtbh


Signalling_Point.Nokia.GSM.MSC_SCCP_Signalling_Point_Subsystem

This section describes the counters of M216 N.B. There is a secondary key of signalling_network and also subsystem

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
allowed_receivedACCUMULATIONINT8Subsystem allowed messages receivedSCCMSC.M216B4C3nkmtbh
cong_receivedACCUMULATIONINT8SCCP/subsystem congested message receivedSCCMSC.M216B4C1nkmtbh
prohibited_receivedACCUMULATIONINT8Subsystem prohibited messages receivedSCCMSC.M216B4C2nkmtbh


Signalling_Point.Nokia.GSM.MSC_Signalling_point_performance

MSC signalling point performance data

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changebacksACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Automatic changebackobsolete.obsolete 
automatic_changeoversACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Automatic changeoverobsolete.obsolete 
dur_in_service_stateACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Duration of signalling link in the in-service stateobsolete.obsolete 
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Signalling link failure - abnormal FIBR/BSNRobsolete.obsolete 
link_failures_ali_or_prov_failACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Signalling link alignment or proving failureobsolete.obsolete 
link_failures_all_reasonsACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Signalling link failures - all reasonsobsolete.obsolete 
link_failures_exc_del_of_ackACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Caused by excessive delay of acknowledgementobsolete.obsolete 
link_failures_exc_dur_of_congACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Signalling link failure - excessive duration of congestionobsolete.obsolete 
link_failures_exc_error_rateACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Signalling link failure - excessive error rateobsolete.obsolete 
link_failures_m_err_ind_sd_losACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) MAA-ERROR indication with Error Type SD lossobsolete.obsolete 
link_restorationsACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Signalling link restorationobsolete.obsolete 
negative_acksACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Number of negative acknowledgements receivedobsolete.obsolete 
sign_units_received_in_errorACCUMULATIONINT8(Obsolete in M13.5, SLPNMSC block now parked under Signalling_Link object) Number of signal units received in errorobsolete.obsolete 


Signalling_Point.Nokia.GSM.MSC_Signalling_Point_Status

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
adjacent_inaccessibleACCUMULATIONINT8Adjacent signalling point inaccessible.STAMSC.M211B2C2nkmtbh
duration_adjacentACCUMULATIONINT8Duration of inaccessibility of adjacent signalling point (seconds, minutes, hours, days).STAMSC.M211B2C1nkmtbh
msgACCUMULATIONINT8The number of transfer controlled messages received.STAMSC.M211B2C3nkmtbh
msu_discarded_routing_recACCUMULATIONINT8The number of message signal units (MSU) discarded due to routing data error (received).STAMSC.M211B2C5nkmtbh
msu_discarded_routing_transACCUMULATIONINT8The number of message signal units (MSU) discarded due to routing data error (transmitted).STAMSC.M211B2C4nkmtbh
msu_stp_opcACCUMULATIONINT8Unauthorised stp msu count for inhibited opc.STAMSC.M211B2C7nkmtbh
msu_stp_spcACCUMULATIONINT8Unauthorised stp msu count for inhibited dpc.STAMSC.M211B2C6nkmtbh
msu_stp_stpACCUMULATIONINT8Unauthorised stp msu count for inhibited stp.STAMSC.M211B2C8nkmtbh
msu_user_part_recACCUMULATIONINT8User Part unavailable MSU received.STAMSC.M211B2C10nkmtbh
msu_user_part_transACCUMULATIONINT8User Part unavailable MSU transmitted.STAMSC.M211B2C9nkmtbh


Signalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic_Matrix

This measurement contains measurement data of one or more signalling points.N.B. There is a secondary key of SIO, origination_point and also destination_point

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, Destination_Point (destination_point_id) , Originating_Point (originating_point_id) and SIO (sio_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
msuACCUMULATIONINT8The number of MSUs handled with given OPC, DPC, SIOMTXMSC.M215B2C2nkmtbh
sif_sioACCUMULATIONINT8The number of SIF and SIO octets handled with given OPC, DPC, SIOMTXMSC.M215B2C1nkmtbh


Signalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic_STP

This section describes the key columns and counters of M213 N.B. There is a secondary key of signalling_transfer_point.

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Transfer_Point (signalling_transfer_point_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_dpcACCUMULATIONINT8The number of transmitted SIF and SIO octets with a given DPC.SIGSMSC.M213B3C1nkmtbh


Signalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic_User

This measurement contains measurement data of one or more MTP user parts.N.B. There is a secondary key of SIO

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and SIO (SIO_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8(Obsolete in M13.5, UTRAMSC block now parked under MSC object) The number of SIF and SIO received with the given SIO.obsolete.obsoletenkmtbh
sif_sio_transACCUMULATIONINT8(Obsolete in M13.5, UTRAMSC block now parked under MSC object) The number of SIF and SIO transmitted with the given SIO.obsolete.obsoletenkmtbh


Signalling_Point.Nokia.GSM.MSC_Signalling_Point_Traffic

This measurement contains measurement data from one or more MTP signalling points

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8The number of received SIF and SIO octets with a given signalling pointSIGMSC.M213B2C1nkmtbh
sif_sio_transACCUMULATIONINT8The total number of transmitted SIF and SIO octets.SIGMSC.M213B2C2nkmtbh


Signalling_Point.Nokia.GSM.MSC_Signalling_Point_Utilisation

MSC signalling point utilisation data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cumulative_duration_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 1).obsolete.obsolete 
cumulative_duration_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 2).obsolete.obsolete 
cumulative_duration_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 3).obsolete.obsolete 
events_res_in_loss_of_msus_l1ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 1).  
events_res_in_loss_of_msus_l2ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 2).obsolete.obsolete 
events_res_in_loss_of_msus_l3ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 3).obsolete.obsolete 
min_30_peak_traf_in_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedobsolete.obsolete 
min_30_peak_traf_out_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedobsolete.obsolete 
min_30_peakload_traffic_inERLANGINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) 30 minutes peak load in milliErlangs for incoming trafficobsolete.obsolete 
min_30_peakload_traffic_outERLANGINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) 30 minutes peak load in milliErlangs for outgoing trafficobsolete.obsolete 
min_5_peak_traf_in_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Start time of the 5 minutes freezing period when the peak congestion for incoming traffic was noticed (Measured as minutes from measurement period start time.)obsolete.obsolete 
min_5_peak_traf_out_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Start time of the 5 minutes freezing period when the peak congestion for outgoing traffic was noticed. (Measured as minutes from measurement period start time.)obsolete.obsolete 
min_5_peakload_traffic_inERLANGINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) 5 minutes peak load in milliErlangs for incoming trafficobsolete.obsolete 
min_5_peakload_traffic_outERLANGINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) 5 minutes peak load in milliErlangs for outgoing trafficobsolete.obsolete 
msus_discarded_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 1).obsolete.obsolete 
msus_discarded_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 2).obsolete.obsolete 
msus_discarded_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 3).obsolete.obsolete 
msus_receivedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of message signal units received.obsolete.obsolete 
msus_transmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of message signal units transmitted.  
octets_retransmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of octets retransmitted.obsolete.obsolete 
sif_and_sio_octets_receivedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of received SIF and SIO octetsobsolete.obsolete 
sif_and_sio_octets_transmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) The number of SIF and SIO octets transmitted.obsolete.obsolete 
sl_congestion_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Signalling link congestion (level 1).obsolete.obsolete 
sl_congestion_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Signalling link congestion (level 2).obsolete.obsolete 
sl_congestion_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNMSC block now parked under Signalling_Link object) Signalling link congestion (level 3).obsolete.obsolete 


Signalling_Point.Nokia.GSM.Signalling_clear_code

Signalling clear code data.

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, MSC_Clear_Code (msc_clear_code_id) and Signal_Protocol (signal_protocol_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sscc_ringACCUMULATIONINT8The number of clear codes in the ringing phase (0...999999999).SPCCC.M136B2C4 
sscc_signallingACCUMULATIONINT8The number of clear codes in the signalling phase (0...999999999).SPCCC.M136B2C3 
sscc_speechACCUMULATIONINT8The number of clear codes in the speech phase (0...999999999).SPCCC.M136B2C5 


Signalling_Point.Nokia.GSM.SRR_Linkset_and_Routeset_Availability

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
duration_link_set_unavailACCUMULATIONINT8Duration of unavailability of signalling link setAVASRR.M212B2C1nksrrotbh
initiation_of_broadcast_tfaACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restoration (4.6 in ITU-T Q.752)AVASRR.M212B2C5nksrrotbh
initiation_of_broadcast_tfpACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failure (4.5 in ITU-T Q.752)AVASRR.M212B2C4nksrrotbh
sr_set_una_due_to_tfp_recACCUMULATIONINT8Unavailability of signalling route set due to transfer prohibited message received (4.7 in ITU-T Q.752)AVASRR.M212B2C6nksrrotbh
sr_set_una_to_given_destACCUMULATIONINT8Unavailability of signalling route set (4.9 in ITU-T Q.752)AVASRR.M212B2C7nksrrotbh
start_time_link_set_failACCUMULATIONINT8Start of signalling link set failure.AVASRR.M212B2C8nksrrotbh
stop_time_link_set_failACCUMULATIONINT8Stop of signalling link set failure.AVASRR.M212B2C9nksrrotbh
transfer_block_link_failACCUMULATIONINT8Transmission of transfer prohibited message started due to signalling link failure.AVASRR.M212B2C2nksrrotbh
transfer_ok_link_upACCUMULATIONINT8Transmission of transfer allowed message started due to signalling link restoration.AVASRR.M212B2C3nksrrotbh


Signalling_Point.Nokia.GSM.SRR_SCCP_Signalling_Point_Errors

This section describes the counters of M216 with respect to errors. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
cr_receivedACCUMULATIONINT8CR messages received from the MTP plus ISDN-UP embedded CRsSCCPSRR.M216B3C2nksrrotbh
cr_transACCUMULATIONINT8CR messages sent to the MTP plus ISDN-UP embedded CRsSCCPSRR.M216B3C1nksrrotbh
cref_receivedACCUMULATIONINT8CREF messages received from the MTPSCCPSRR.M216B3C4nksrrotbh
cref_transACCUMULATIONINT8CREF messages sent to the MTPSCCPSRR.M216B3C3nksrrotbh
err_receivedACCUMULATIONINT8ERR messages received from the MTPSCCPSRR.M216B3C8nksrrotbh
err_transACCUMULATIONINT8ERR messages sent to the MTPSCCPSRR.M216B3C7nksrrotbh
gt1_failACCUMULATIONINT8Routing error - no translation of GT type 1SCCPSRR.M216B2C1nksrrotbh
gt2_failACCUMULATIONINT8Routing error - no translation of GT type 2SCCPSRR.M216B2C2nksrrotbh
ludt_receivedACCUMULATIONINT8LUDT messages receivedSCCPSRR.M216B2C23nksrrotbh
ludt_transACCUMULATIONINT8LUDT messages sentSCCPSRR.M216B2C22nksrrotbh
ludts_receivedACCUMULATIONINT8LUDTS messages receivedSCCPSRR.M216B2C25nksrrotbh
rsr_receivedACCUMULATIONINT8RSR messages received from the MTPSCCPSRR.M216B3C6nksrrotbh
rsr_transACCUMULATIONINT8RSR messages sent to the MTPSCCPSRR.M216B3C5nksrrotbh
udt_receivedACCUMULATIONINT8UDT messages receivedSCCPSRR.M216B2C15nksrrotbh
udt_transACCUMULATIONINT8UDT messages sentSCCPSRR.M216B2C14nksrrotbh
udts_receivedACCUMULATIONINT8UDTS messages receivedSCCPSRR.M216B2C17nksrrotbh
udts_transACCUMULATIONINT8UDTS messages sentSCCPSRR.M216B2C16nksrrotbh
xudt_receivedACCUMULATIONINT8XUDT messages receivedSCCPSRR.M216B2C19nksrrotbh
xudt_transACCUMULATIONINT8XUDT messages sentSCCPSRR.M216B2C18nksrrotbh
xudts_receivedACCUMULATIONINT8XUDTS messages receivedSCCPSRR.M216B2C21nksrrotbh
xudts_transACCUMULATIONINT8XUDTS messages sentSCCPSRR.M216B2C20nksrrotbh


Signalling_Point.Nokia.GSM.SRR_SCCP_Signalling_Point_Messages

This section describes the counters of M216 with respect to messages. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_release_complete_class2ACCUMULATIONINT8Failure of release complete supervision, protocol class 2SCCPSRR.M216B3C9nksrrotbh
err_release_complete_class3ACCUMULATIONINT8Failure of release complete supervision, protocol class 3SCCPSRR.M216B3C10nksrrotbh
gt_translationACCUMULATIONINT8Routing error - no translation of a specific GTSCCPSRR.M216B2C6nksrrotbh
gt_unknownACCUMULATIONINT8Routing error - no translation of unknown GT typeSCCPSRR.M216B2C5nksrrotbh
gt3_failACCUMULATIONINT8Routing error - no translation of GT type 3SCCPSRR.M216B2C3nksrrotbh
gt4_failACCUMULATIONINT8Routing error - no translation of GT type 4SCCPSRR.M216B2C4nksrrotbh
ludts_transACCUMULATIONINT8LUDTS messages sentSCCPSRR.M216B2C24nksrrotbh
net_failACCUMULATIONINT8Routing error - due to a failure in the networkSCCPSRR.M216B2C7nksrrotbh
net_overloadACCUMULATIONINT8Routing error - due to network overloadSCCPSRR.M216B2C8nksrrotbh
provider_connection_releaseACCUMULATIONINT8Provider initiated release of a connectionSCCPSRR.M216B3C14nksrrotbh
provider_connection_resetACCUMULATIONINT8Provider initiated reset of a connectionSCCPSRR.M216B3C13nksrrotbh
subsystem_failACCUMULATIONINT8Routing error - due to a failure in the subsystemSCCPSRR.M216B2C9nksrrotbh
subsystem_overloadACCUMULATIONINT8Routing error - due to subsystem overloadSCCPSRR.M216B2C10nksrrotbh
syntax_errorACCUMULATIONINT8Observed syntax errorsSCCPSRR.M216B2C13nksrrotbh
timer_expiry_class2ACCUMULATIONINT8Timer T(iar) expiry, protocol class 2SCCPSRR.M216B3C11nksrrotbh
timer_expiry_class3ACCUMULATIONINT8Timer T(iar) expiry, protocol class 3SCCPSRR.M216B3C12nksrrotbh
unequipped_userACCUMULATIONINT8Routing error - unequipped userSCCPSRR.M216B2C11nksrrotbh
unknown_reasonACCUMULATIONINT8Routing error - unknown userSCCPSRR.M216B2C12nksrrotbh


Signalling_Point.Nokia.GSM.SRR_SCCP_Signalling_Point_Subsystem

This section describes the counters of M216: N.B. There is a secondary key of signalling_network and subsystem

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
allowed_receivedACCUMULATIONINT8Subsystem allowed messages receivedSCCSRR.M216B4C3nksrrotbh
cong_receivedACCUMULATIONINT8SCCP/subsystem congested message receivedSCCSRR.M216B4C1nksrrotbh
prohibited_receivedACCUMULATIONINT8Subsystem prohibited messages receivedSCCSRR.M216B4C2nksrrotbh


Signalling_Point.Nokia.GSM.SRR_Signalling_point_performance

SRR signalling point performance data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
automatic_changebacksACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Automatic changebackobsolete.obsolete 
automatic_changeoversACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Automatic changeoverobsolete.obsolete 
dur_in_service_stateACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Duration of signalling link in the in-service stateobsolete.obsolete 
link_failures_abnorm_fibr_bsnrACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Signalling link failure - abnormal FIBR/BSNRobsolete.obsolete 
link_failures_ali_or_prov_failACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Signalling link alignment or proving failureobsolete.obsolete 
link_failures_all_reasonsACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Signalling link failures - all reasonsobsolete.obsolete 
link_failures_exc_del_of_ackACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Caused by excessive delay of acknowledgementobsolete.obsolete 
link_failures_exc_dur_of_congACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Signalling link failure - excessive duration of congestionobsolete.obsolete 
link_failures_exc_error_rateACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Signalling link failure - excessive error rateobsolete.obsolete 
link_failures_m_err_ind_sd_losACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) MAA-ERROR indication with Error Type SD lossobsolete.obsolete 
link_restorationsACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Signalling link restorationobsolete.obsolete 
negative_acksACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Number of negative acknowledgements receivedobsolete.obsolete 
sign_units_received_in_errorACCUMULATIONINT8 (Obsolete in M13.5, SLPNSRR block now parked under Signalling_Link object) Number of signal units received in errorobsolete.obsolete 


Signalling_Point.Nokia.GSM.SRR_Signalling_Point_Status

This measurement contains measurement data of one or more MTP signalling links.

KPITypeData TypeDescriptionDerivationAdditional Summaries
adjacent_inaccessibleACCUMULATIONINT8Adjacent signalling point inaccessible.STASRR.M211B2C2nksrrotbh
duration_adjacentACCUMULATIONINT8Duration of inaccessibility of adjacent signalling point (seconds, minutes, hours, days).STASRR.M211B2C1nksrrotbh
msgACCUMULATIONINT8The number of transfer controlled messages received.STASRR.M211B2C3nksrrotbh
msu_discarded_routing_recACCUMULATIONINT8The number of message signal units (MSU) discarded due to routing data error (received).STASRR.M211B2C5nksrrotbh
msu_discarded_routing_transACCUMULATIONINT8The number of message signal units (MSU) discarded due to routing data error (transmitted).STASRR.M211B2C4nksrrotbh
msu_stp_opcACCUMULATIONINT8Unauthorised stp msu count for inhibited opc.STASRR.M211B2C7nksrrotbh
msu_stp_spcACCUMULATIONINT8Unauthorised stp msu count for inhibited dpc.STASRR.M211B2C6nksrrotbh
msu_stp_stpACCUMULATIONINT8Unauthorised stp msu count for inhibited stp.STASRR.M211B2C8nksrrotbh
msu_user_part_recACCUMULATIONINT8User Part unavailable MSU received.STASRR.M211B2C10nksrrotbh
msu_user_part_transACCUMULATIONINT8User Part unavailable MSU transmitted.STASRR.M211B2C9nksrrotbh


Signalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic_Matrix

This measurement contains measurement data of one or more signalling points. N.B. There is a secondary key of SIO, origination_point and destination_point

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point, Destination_Point (destination_point_id) , Originating_Point (originating_point_id) and SIO (sio_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
msuACCUMULATIONINT8The number of MSUs handled with given OPC, DPC, SIOMTXSRR.M215B2C2nksrrotbh
sif_sioACCUMULATIONINT8The number of SIF and SIO octets handled with given OPC, DPC, SIOMTXSRR.M215B2C1nksrrotbh


Signalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic_STP

This section describes the key columns and counters of M213. N.B. There is a secondary key of signalling_transfer_point

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and Signalling_Transfer_Point (signalling_transfer_point_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_dpcACCUMULATIONINT8The number of transmitted SIF and SIO octets with a given DPC.SIGSSRR.M213B3C1nksrrotbh


Signalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic_User

This measurement contains measurement data of one or more MTP user parts. N.B. There is a secondary key of SIO

The performance data measurements for this KPI group are recorded against the combination of Signalling_Point and SIO (sio_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8(Obsolete in M13.5, UTRASRR block now parked under SRR object) The number of SIF and SIO received with the given SIO.obsolete.obsoletenksrrotbh
sif_sio_transACCUMULATIONINT8(Obsolete in M13.5, UTRASRR block now parked under SRR object) The number of SIF and SIO transmitted with the given SIO.obsolete.obsoletenksrrotbh


Signalling_Point.Nokia.GSM.SRR_Signalling_Point_Traffic

This measurement contains measurement data from one or more MTP signalling points

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8The number of received SIF and SIO octets with a given signalling pointSIGSRR.M213B2C1nksrrotbh
sif_sio_transACCUMULATIONINT8The total number of transmitted SIF and SIO octets.SIGSRR.M213B2C2nksrrotbh


Signalling_Point.Nokia.GSM.SRR_Signalling_Point_Utilisation

SRR signalling point utilisation data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
cumulative_duration_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 1).obsolete.obsolete 
cumulative_duration_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 2).obsolete.obsolete 
cumulative_duration_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Cumulative duration of signalling link congestion (level 3).obsolete.obsolete 
events_res_in_loss_of_msus_l1ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 1).obsolete.obsolete 
events_res_in_loss_of_msus_l2ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 2).obsolete.obsolete 
events_res_in_loss_of_msus_l3ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of congestion events resulting in loss of MSUs (level 3).obsolete.obsolete 
min_30_peak_traf_in_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Start time of the 30-minute freezing period when the peak congestion for the incoming traffic was noticedobsolete.obsolete 
min_30_peak_traf_out_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Start time of the 30-minute freezing period when the peak congestion for the outgoing traffic was noticedobsolete.obsolete 
min_30_peakload_traffic_inERLANGINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) 30 minutes peak load in milliErlangs for incoming trafficobsolete.obsolete 
min_30_peakload_traffic_outERLANGINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) 30 minutes peak load in milliErlangs for outgoing trafficobsolete.obsolete 
min_5_peak_traf_in_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Start time of the 5 minutes freezing period when the peak congestion for incoming traffic was noticed (Measured as minutes from measurement period start time.)obsolete.obsolete 
min_5_peak_traf_out_startedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Start time of the 5 minutes freezing period when the peak congestion for outgoing traffic was noticed. (Measured as minutes from measurement period start time.)obsolete.obsolete 
min_5_peakload_traffic_inERLANGINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) 5 minutes peak load in milliErlangs for incoming trafficobsolete.obsolete 
min_5_peakload_traffic_outERLANGINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) 5 minutes peak load in milliErlangs for outgoing trafficobsolete.obsolete 
msus_discarded_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 1).obsolete.obsolete 
msus_discarded_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 2).obsolete.obsolete 
msus_discarded_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of message signal units (MSU) discarded due to signalling link congestion (level 3).obsolete.obsolete 
msus_receivedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of message signal units received.obsolete.obsolete 
msus_transmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of message signal units transmitted.obsolete.obsolete 
octets_retransmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of octets retransmitted.obsolete.obsolete 
sif_and_sio_octets_receivedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of received SIF and SIO octetsobsolete.obsolete 
sif_and_sio_octets_transmittedACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) The number of SIF and SIO octets transmitted.obsolete.obsolete 
sl_congestion_level1ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Signalling link congestion (level 1).obsolete.obsolete 
sl_congestion_level2ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Signalling link congestion (level 2).obsolete.obsolete 
sl_congestion_level3ACCUMULATIONINT8(Obsolete in M13.5, MTPNSRR block now parked under Signalling_Link object) Signalling link congestion (level 3).obsolete.obsolete 


SIP_Interface Performance Indicators

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


SIP_Interface.Nokia.GSM.SIP_Requests

SIP request counters

The performance data measurements for this KPI group are recorded against the combination of SIP_Interface and SIP_Method (sip_method_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIP_PROT_TOT_LEN_RECV_REQSACCUMULATIONINT8Shows the total length of incoming SIP requests in kilobytes.SIPPMETH.M360B3C2nksipreqbh
SIP_PROT_TOT_LEN_RECV_RESPSACCUMULATIONINT8Shows the length of the received responses in kilobytes.SIPPMETH.M360B3C6nksipreqbh
SIP_PROT_TOT_LEN_SENT_REQSACCUMULATIONINT8Shows the total length of outgoing SIP requests in kilobytes.SIPPMETH.M360B3C4nksipreqbh
SIP_PROT_TOT_LEN_SENT_RESPSACCUMULATIONINT8Shows the length of the sent responses in kilobytes.SIPPMETH.M360B3C8nksipreqbh
SIP_PROT_TOT_NUM_RECV_REQSACCUMULATIONINT8Shows the sum of incoming SIP requests.SIPPMETH.M360B3C1nksipreqbh
SIP_PROT_TOT_NUM_RECV_RESPSACCUMULATIONINT8Shows the sum of the different received SIP responses for one method.SIPPMETH.M360B3C5nksipreqbh
SIP_PROT_TOT_NUM_REQSACCUMULATIONINT8Shows the sum of incoming and outgoing SIP requests.SIPPMETH.M360B3C1 + M360B3C3nksipreqbh
SIP_PROT_TOT_NUM_SENT_REQSACCUMULATIONINT8Shows the sum of outgoing SIP requests.SIPPMETH.M360B3C3nksipreqbh
SIP_PROT_TOT_NUM_SENT_RESPSACCUMULATIONINT8Shows the sum of the different sent SIP responses for one method.SIPPMETH.M360B3C7nksipreqbh


SIP_Interface.Nokia.GSM.SIP_Responses

SIP Response related counters

The performance data measurements for this KPI group are recorded against the combination of SIP_Interface and SIP_Response (sip_response_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
SIP_PROT_AMOUNT_RECV_RESPSACCUMULATIONINT8Shows the amount of one particular received SIP responses for one method.SIPPRESP.M360B4C1nksipreqbh
SIP_PROT_AMOUNT_SENT_RESPSACCUMULATIONINT8Shows the amount of one particular sent SIP response for one method.SIPPRESP.M360B4C2nksipreqbh


SMSC Performance Indicators

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


SMSC.Nokia.GSM.SMS_Measurements_All_MSC_Types

SMS Measurements for ALL MSC types

KPITypeData TypeDescriptionDerivationAdditional Summaries
smsc_perm_fail_gmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a permanent error.SMS.M309B6C3nksmstbh
smsc_perm_fail_vmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a permanent error.SMS.M309B7C3nksmstbh
smsc_succ_gmsc_mt_physACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMS.M309B6C1nksmstbh
smsc_succ_iwmsc_mo_logicalACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DWSMS.M309B4C1nksmstbh
smsc_succ_iwmsc_mo_physicalACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMS.M309B5C1nksmstbh
smsc_succ_vmsc_mo_logicalACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMS.M309B3C1nksmstbh
smsc_succ_vmsc_mt_physACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMS.M309B7C1nksmstbh
smsc_temp_fail_gmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a temporary error. If the subscriber cannot be reached, or the mobile memory is exceeded, it could cause a temporary error.SMS.M309B6C2nksmstbh
smsc_temp_fail_vmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a temporary error. If the subscriber cannot be reached, or the mobile memory is exceeded, it could cause a temporary error.SMS.M309B7C2nksmstbh
smsc_unsucc_iwmsc_mo_logicalACCUMULATIONINT8The number of unsuccessful SMs ( PERM and TEMP FAIL ).SMS.M309B4C2nksmstbh
smsc_unsucc_iwmsc_mo_physicalACCUMULATIONINT8The number of unsuccessful SMs ( PERM and TEMP FAIL ).SMS.M309B5C2nksmstbh
smsc_unsucc_vmsc_mo_logicalACCUMULATIONINT8The number of unsuccessful SMs ( PERM and TEMP FAIL ).SMS.M309B3C2nksmstbh


SMSC.Nokia.GSM.SMS_Measurements

This section describes the SMS measurement.

KPITypeData TypeDescriptionDerivationAdditional Summaries
all_smsACCUMULATIONINT8The total number of SMS.{smsc_perm_fail_gmsc_mt_phys} + {smsc_perm_fail_vmsc_mt_phys} + {smsc_succ_gmsc_mt_phys} + {smsc_succ_iwmsc_mo_logical} + {smsc_succ_iwmsc_mo_physical} + {smsc_succ_vmsc_mo_logical} + {smsc_succ_vmsc_mt_phys} + {smsc_temp_fail_gmsc_mt_phys} + {smsc_temp_fail_vmsc_mt_phys} + {smsc_unsucc_iwmsc_mo_logical} + {smsc_unsucc_iwmsc_mo_physical} + {smsc_unsucc_vmsc_mo_logical}nksmstbh
smsc_perm_fail_gmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a permanent error.SMSTY.M309B6C3 or SMSTY_AGGR.M309B6C3nksmstbh
smsc_perm_fail_vmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a permanent error.SMSTY.M309B7C3 or SMSTY_AGGR.M309B7C3nksmstbh
smsc_succ_gmsc_mt_physACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMSTY.M309B6C1 or SMSTY_AGGR.M309B6C1nksmstbh
smsc_succ_iwmsc_mo_logicalACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DWSMSTY.M309B4C1 or SMSTY_AGGR.M309B4C1nksmstbh
smsc_succ_iwmsc_mo_physicalACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMSTY.M309B5C1 or SMSTY_AGGR.M309B5C1nksmstbh
smsc_succ_vmsc_mo_logicalACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMSTY.M309B3C1 or SMSTY_AGGR.M309B3C1nksmstbh
smsc_succ_vmsc_mt_physACCUMULATIONINT8The number of successful SMs. The counter is updated for the clear code of 0x0. CODING: DW,SMSTY.M309B7C1 or SMSTY_AGGR.M309B7C1nksmstbh
smsc_temp_fail_gmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a temporary error. If the subscriber cannot be reached, or the mobile memory is exceeded, it could cause a temporary error.SMSTY.M309B6C2 or SMSTY_AGGR.M309B6C2nksmstbh
smsc_temp_fail_vmsc_mt_physACCUMULATIONINT8The number of unsuccessful SMs caused by a temporary error. If the subscriber cannot be reached, or the mobile memory is exceeded, it could cause a temporary error.SMSTY.M309B7C2 or SMSTY_AGGR.M309B7C2nksmstbh
smsc_unsucc_iwmsc_mo_logicalACCUMULATIONINT8The number of unsuccessful SMs ( PERM and TEMP FAIL ).SMSTY.M309B4C2 or SMSTY_AGGR.M309B4C2nksmstbh
smsc_unsucc_iwmsc_mo_physicalACCUMULATIONINT8The number of unsuccessful SMs ( PERM and TEMP FAIL ).SMSTY.M309B5C2 or SMSTY_AGGR.M309B5C2nksmstbh
smsc_unsucc_vmsc_mo_logicalACCUMULATIONINT8The number of unsuccessful SMs ( PERM and TEMP FAIL ).SMSTY.M309B3C2 or SMSTY_AGGR.M309B3C2nksmstbh


SONET_SDH_Protection_Group Performance Indicators

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


SONET_SDH_Protection_Group.Nokia.GSM.Protection

Protection Group stats

KPITypeData TypeDescriptionDerivationAdditional Summaries
SDH_PROT_PSCACCUMULATIONINT8Counts the number of occurred protection switches.SONSDH.M516B2C3 
SDH_PROT_PSDACCUMULATIONINT8The PSD counts how long (in seconds) the traffic has been in protection section.SONSDH.M516B2C4 


SRR Performance Indicators

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


SRR.Nokia.GSM.Operation_AnyTimeInterrogation

SRR Operation measurements for AnyTimeInterrogation operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
anytimeinterr_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B4C26nksrrotbh
anytimeinterr_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B4C16nksrrotbh
anytimeinterr_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B4C19nksrrotbh
anytimeinterr_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B4C18nksrrotbh
anytimeinterr_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B4C5nksrrotbh
anytimeinterr_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B4C2nksrrotbh
anytimeinterr_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B4C28nksrrotbh
anytimeinterr_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B4C24nksrrotbh
anytimeinterr_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B4C22nksrrotbh
anytimeinterr_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B4C23nksrrotbh
anytimeinterr_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B4C27nksrrotbh
anytimeinterr_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B4C6nksrrotbh
anytimeinterr_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B4C17nksrrotbh
anytimeinterr_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B4C25nksrrotbh
anytimeinterr_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B4C12nksrrotbh
anytimeinterr_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B4C13nksrrotbh
anytimeinterr_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B4C14nksrrotbh
anytimeinterr_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B4C15nksrrotbh
anytimeinterr_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B4C4nksrrotbh
anytimeinterr_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B4C8nksrrotbh
anytimeinterr_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B4C9nksrrotbh
anytimeinterr_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B4C10nksrrotbh
anytimeinterr_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B4C11nksrrotbh
anytimeinterr_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B4C3nksrrotbh
anytimeinterr_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B4C1nksrrotbh
anytimeinterr_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B4C7nksrrotbh
anytimeinterr_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B4C20nksrrotbh
anytimeinterr_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B4C21nksrrotbh


SRR.Nokia.GSM.Operation_CCBS_Request

SRR Operation measurements for CCBS Request operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ccbsrequest_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B9C26nksrrotbh
ccbsrequest_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B9C16nksrrotbh
ccbsrequest_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B9C19nksrrotbh
ccbsrequest_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B9C18nksrrotbh
ccbsrequest_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B9C5nksrrotbh
ccbsrequest_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B9C2nksrrotbh
ccbsrequest_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B9C28nksrrotbh
ccbsrequest_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B9C24nksrrotbh
ccbsrequest_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B9C22nksrrotbh
ccbsrequest_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B9C23nksrrotbh
ccbsrequest_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B9C27nksrrotbh
ccbsrequest_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B9C6nksrrotbh
ccbsrequest_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B9C17nksrrotbh
ccbsrequest_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B9C25nksrrotbh
ccbsrequest_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B9C12nksrrotbh
ccbsrequest_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B9C13nksrrotbh
ccbsrequest_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B9C14nksrrotbh
ccbsrequest_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B9C15nksrrotbh
ccbsrequest_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B9C4nksrrotbh
ccbsrequest_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B9C8nksrrotbh
ccbsrequest_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B9C9nksrrotbh
ccbsrequest_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B9C10nksrrotbh
ccbsrequest_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B9C11nksrrotbh
ccbsrequest_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B9C3nksrrotbh
ccbsrequest_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B9C1nksrrotbh
ccbsrequest_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B9C7nksrrotbh
ccbsrequest_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B9C20nksrrotbh
ccbsrequest_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B9C21nksrrotbh


SRR.Nokia.GSM.Operation_InitialDP_CAP

SRR Operation measurements for InitialDP CAP operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
initialdpcap_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B18C26nksrrotbh
initialdpcap_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B18C16nksrrotbh
initialdpcap_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B18C19nksrrotbh
initialdpcap_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B18C18nksrrotbh
initialdpcap_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B18C5nksrrotbh
initialdpcap_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B18C2nksrrotbh
initialdpcap_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B18C28nksrrotbh
initialdpcap_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B18C24nksrrotbh
initialdpcap_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B18C22nksrrotbh
initialdpcap_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B18C23nksrrotbh
initialdpcap_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B18C27nksrrotbh
initialdpcap_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B18C6nksrrotbh
initialdpcap_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B18C17nksrrotbh
initialdpcap_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B18C25nksrrotbh
initialdpcap_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B18C12nksrrotbh
initialdpcap_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B18C13nksrrotbh
initialdpcap_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B18C14nksrrotbh
initialdpcap_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B18C15nksrrotbh
initialdpcap_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B18C4nksrrotbh
initialdpcap_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B18C8nksrrotbh
initialdpcap_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B18C9nksrrotbh
initialdpcap_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B18C10nksrrotbh
initialdpcap_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B18C11nksrrotbh
initialdpcap_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B18C3nksrrotbh
initialdpcap_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B18C1nksrrotbh
initialdpcap_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B18C7nksrrotbh
initialdpcap_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B18C20nksrrotbh
initialdpcap_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B18C21nksrrotbh


SRR.Nokia.GSM.Operation_InitialDP_INAP

SRR Operation measurements for InitialDP INAP operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
initialdp_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B16C26nksrrotbh
initialdp_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B16C16nksrrotbh
initialdp_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B16C19nksrrotbh
initialdp_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B16C18nksrrotbh
initialdp_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B16C5nksrrotbh
initialdp_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B16C2nksrrotbh
initialdp_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B16C28nksrrotbh
initialdp_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B16C24nksrrotbh
initialdp_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B16C22nksrrotbh
initialdp_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B16C23nksrrotbh
initialdp_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B16C27nksrrotbh
initialdp_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B16C6nksrrotbh
initialdp_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B16C17nksrrotbh
initialdp_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B16C25nksrrotbh
initialdp_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B16C12nksrrotbh
initialdp_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B16C13nksrrotbh
initialdp_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B16C14nksrrotbh
initialdp_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B16C15nksrrotbh
initialdp_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B16C4nksrrotbh
initialdp_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B16C8nksrrotbh
initialdp_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B16C9nksrrotbh
initialdp_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B16C10nksrrotbh
initialdp_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B16C11nksrrotbh
initialdp_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B16C3nksrrotbh
initialdp_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B16C1nksrrotbh
initialdp_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B16C7nksrrotbh
initialdp_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B16C20nksrrotbh
initialdp_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B16C21nksrrotbh


SRR.Nokia.GSM.Operation_RestoreData

SRR Operation measurements for RestoreData operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
restoredata_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B15C26nksrrotbh
restoredata_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B15C16nksrrotbh
restoredata_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B15C19nksrrotbh
restoredata_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B15C18nksrrotbh
restoredata_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B15C5nksrrotbh
restoredata_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B15C2nksrrotbh
restoredata_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B15C28nksrrotbh
restoredata_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B15C24nksrrotbh
restoredata_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B15C22nksrrotbh
restoredata_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B15C23nksrrotbh
restoredata_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B15C27nksrrotbh
restoredata_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B15C6nksrrotbh
restoredata_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B15C17nksrrotbh
restoredata_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B15C25nksrrotbh
restoredata_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B15C12nksrrotbh
restoredata_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B15C13nksrrotbh
restoredata_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B15C14nksrrotbh
restoredata_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B15C15nksrrotbh
restoredata_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B15C4nksrrotbh
restoredata_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B15C8nksrrotbh
restoredata_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B15C9nksrrotbh
restoredata_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B15C10nksrrotbh
restoredata_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B15C11nksrrotbh
restoredata_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B15C3nksrrotbh
restoredata_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B15C1nksrrotbh
restoredata_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B15C7nksrrotbh
restoredata_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B15C20nksrrotbh
restoredata_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B15C21nksrrotbh


SRR.Nokia.GSM.Operation_SendAuthenticationInfo

SRR Operation measurements for SendAuthenticationInfo operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sendautheinfo_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B12C26nksrrotbh
sendautheinfo_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B12C16nksrrotbh
sendautheinfo_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B12C19nksrrotbh
sendautheinfo_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B12C18nksrrotbh
sendautheinfo_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B12C5nksrrotbh
sendautheinfo_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B12C2nksrrotbh
sendautheinfo_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B12C28nksrrotbh
sendautheinfo_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B12C24nksrrotbh
sendautheinfo_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B12C22nksrrotbh
sendautheinfo_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B12C23nksrrotbh
sendautheinfo_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B12C27nksrrotbh
sendautheinfo_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B12C6nksrrotbh
sendautheinfo_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B12C17nksrrotbh
sendautheinfo_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B12C25nksrrotbh
sendautheinfo_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B12C12nksrrotbh
sendautheinfo_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B12C13nksrrotbh
sendautheinfo_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B12C14nksrrotbh
sendautheinfo_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B12C15nksrrotbh
sendautheinfo_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B12C4nksrrotbh
sendautheinfo_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B12C8nksrrotbh
sendautheinfo_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B12C9nksrrotbh
sendautheinfo_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B12C10nksrrotbh
sendautheinfo_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B12C11nksrrotbh
sendautheinfo_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B12C3nksrrotbh
sendautheinfo_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B12C1nksrrotbh
sendautheinfo_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B12C7nksrrotbh
sendautheinfo_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B12C20nksrrotbh
sendautheinfo_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B12C21nksrrotbh


SRR.Nokia.GSM.Operation_SendImsi

SRR Operation measurements for SendImsi operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sendimsi_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B6C26nksrrotbh
sendimsi_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B6C16nksrrotbh
sendimsi_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B6C19nksrrotbh
sendimsi_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B6C18nksrrotbh
sendimsi_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B6C5nksrrotbh
sendimsi_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B6C2nksrrotbh
sendimsi_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B6C28nksrrotbh
sendimsi_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B6C24nksrrotbh
sendimsi_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B6C22nksrrotbh
sendimsi_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B6C23nksrrotbh
sendimsi_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B6C27nksrrotbh
sendimsi_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B6C6nksrrotbh
sendimsi_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B6C17nksrrotbh
sendimsi_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B6C25nksrrotbh
sendimsi_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B6C12nksrrotbh
sendimsi_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B6C13nksrrotbh
sendimsi_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B6C14nksrrotbh
sendimsi_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B6C15nksrrotbh
sendimsi_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B6C4nksrrotbh
sendimsi_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B6C8nksrrotbh
sendimsi_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B6C9nksrrotbh
sendimsi_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B6C10nksrrotbh
sendimsi_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B6C11nksrrotbh
sendimsi_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B6C3nksrrotbh
sendimsi_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B6C1nksrrotbh
sendimsi_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B6C7nksrrotbh
sendimsi_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B6C20nksrrotbh
sendimsi_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B6C21nksrrotbh


SRR.Nokia.GSM.Operation_SendParameters

SRR Operation measurements for SendParameters operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sendparameter_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B13C26nksrrotbh
sendparameter_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B13C16nksrrotbh
sendparameter_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B13C19nksrrotbh
sendparameter_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B13C18nksrrotbh
sendparameter_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B13C5nksrrotbh
sendparameter_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B13C2nksrrotbh
sendparameter_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B13C28nksrrotbh
sendparameter_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B13C24nksrrotbh
sendparameter_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B13C22nksrrotbh
sendparameter_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B13C23nksrrotbh
sendparameter_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B13C27nksrrotbh
sendparameter_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B13C6nksrrotbh
sendparameter_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B13C17nksrrotbh
sendparameter_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B13C25nksrrotbh
sendparameter_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B13C12nksrrotbh
sendparameter_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B13C13nksrrotbh
sendparameter_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B13C14nksrrotbh
sendparameter_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B13C15nksrrotbh
sendparameter_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B13C4nksrrotbh
sendparameter_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B13C8nksrrotbh
sendparameter_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B13C9nksrrotbh
sendparameter_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B13C10nksrrotbh
sendparameter_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B13C11nksrrotbh
sendparameter_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B13C3nksrrotbh
sendparameter_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B13C1nksrrotbh
sendparameter_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B13C7nksrrotbh
sendparameter_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B13C20nksrrotbh
sendparameter_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B13C21nksrrotbh


SRR.Nokia.GSM.Operation_SendRoutingInfoForSM

SRR Operation measurements for SendRoutingInfoForSM operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sriforsm_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B3C26nksrrotbh
sriforsm_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B3C16nksrrotbh
sriforsm_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B3C19nksrrotbh
sriforsm_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B3C18nksrrotbh
sriforsm_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B3C5nksrrotbh
sriforsm_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B3C2nksrrotbh
sriforsm_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B3C28nksrrotbh
sriforsm_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B3C24nksrrotbh
sriforsm_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B3C22nksrrotbh
sriforsm_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B3C23nksrrotbh
sriforsm_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B3C27nksrrotbh
sriforsm_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B3C6nksrrotbh
sriforsm_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B3C17nksrrotbh
sriforsm_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B3C25nksrrotbh
sriforsm_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B3C12nksrrotbh
sriforsm_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B3C13nksrrotbh
sriforsm_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B3C14nksrrotbh
sriforsm_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B3C15nksrrotbh
sriforsm_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B3C4nksrrotbh
sriforsm_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B3C8nksrrotbh
sriforsm_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B3C9nksrrotbh
sriforsm_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B3C10nksrrotbh
sriforsm_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B3C11nksrrotbh
sriforsm_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B3C3nksrrotbh
sriforsm_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B3C1nksrrotbh
sriforsm_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B3C7nksrrotbh
sriforsm_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B3C20nksrrotbh
sriforsm_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B3C21nksrrotbh


SRR.Nokia.GSM.Operation_SendRoutingInformationForLCS

SRR Operation measurements for SendRoutingInformationForLCS operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sriforlcs_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B5C26nksrrotbh
sriforlcs_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B5C16nksrrotbh
sriforlcs_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B5C19nksrrotbh
sriforlcs_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B5C18nksrrotbh
sriforlcs_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B5C5nksrrotbh
sriforlcs_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B5C2nksrrotbh
sriforlcs_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B5C28nksrrotbh
sriforlcs_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B5C24nksrrotbh
sriforlcs_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B5C22nksrrotbh
sriforlcs_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B5C23nksrrotbh
sriforlcs_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B5C27nksrrotbh
sriforlcs_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B5C6nksrrotbh
sriforlcs_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B5C17nksrrotbh
sriforlcs_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B5C25nksrrotbh
sriforlcs_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B5C12nksrrotbh
sriforlcs_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B5C13nksrrotbh
sriforlcs_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B5C14nksrrotbh
sriforlcs_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B5C15nksrrotbh
sriforlcs_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B5C4nksrrotbh
sriforlcs_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B5C8nksrrotbh
sriforlcs_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B5C9nksrrotbh
sriforlcs_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B5C10nksrrotbh
sriforlcs_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B5C11nksrrotbh
sriforlcs_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B5C3nksrrotbh
sriforlcs_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B5C1nksrrotbh
sriforlcs_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B5C7nksrrotbh
sriforlcs_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B5C20nksrrotbh
sriforlcs_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B5C21nksrrotbh


SRR.Nokia.GSM.Operation_SendRoutingInformation

SRR Operation measurements for SendRoutingInformation operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sendroutiinfo_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B1C26nksrrotbh
sendroutiinfo_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B1C16nksrrotbh
sendroutiinfo_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B1C19nksrrotbh
sendroutiinfo_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B1C18nksrrotbh
sendroutiinfo_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B1C5nksrrotbh
sendroutiinfo_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B1C2nksrrotbh
sendroutiinfo_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B1C28nksrrotbh
sendroutiinfo_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B1C24nksrrotbh
sendroutiinfo_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B1C22nksrrotbh
sendroutiinfo_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B1C23nksrrotbh
sendroutiinfo_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B1C27nksrrotbh
sendroutiinfo_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B1C6nksrrotbh
sendroutiinfo_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B1C17nksrrotbh
sendroutiinfo_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B1C25nksrrotbh
sendroutiinfo_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B1C12nksrrotbh
sendroutiinfo_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B1C13nksrrotbh
sendroutiinfo_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B1C14nksrrotbh
sendroutiinfo_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B1C15nksrrotbh
sendroutiinfo_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B1C4nksrrotbh
sendroutiinfo_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B1C8nksrrotbh
sendroutiinfo_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B1C9nksrrotbh
sendroutiinfo_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B1C10nksrrotbh
sendroutiinfo_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B1C11nksrrotbh
sendroutiinfo_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B1C3nksrrotbh
sendroutiinfo_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B1C1nksrrotbh
sendroutiinfo_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B1C7nksrrotbh
sendroutiinfo_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B1C20nksrrotbh
sendroutiinfo_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B1C21nksrrotbh


SRR.Nokia.GSM.Operation_SendRoutingInformationWithSOR

SRR Operation measurements for SendRoutingInformationWithSOR operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sriwithsor_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B2C26nksrrotbh
sriwithsor_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B2C16nksrrotbh
sriwithsor_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B2C19nksrrotbh
sriwithsor_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B2C18nksrrotbh
sriwithsor_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B2C5nksrrotbh
sriwithsor_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B2C2nksrrotbh
sriwithsor_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B2C28nksrrotbh
sriwithsor_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B2C24nksrrotbh
sriwithsor_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B2C22nksrrotbh
sriwithsor_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B2C23nksrrotbh
sriwithsor_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B2C27nksrrotbh
sriwithsor_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B2C6nksrrotbh
sriwithsor_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B2C17nksrrotbh
sriwithsor_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B2C25nksrrotbh
sriwithsor_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B2C12nksrrotbh
sriwithsor_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B2C13nksrrotbh
sriwithsor_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B2C14nksrrotbh
sriwithsor_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B2C15nksrrotbh
sriwithsor_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B2C4nksrrotbh
sriwithsor_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B2C8nksrrotbh
sriwithsor_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B2C9nksrrotbh
sriwithsor_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B2C10nksrrotbh
sriwithsor_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B2C11nksrrotbh
sriwithsor_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B2C3nksrrotbh
sriwithsor_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B2C1nksrrotbh
sriwithsor_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B2C7nksrrotbh
sriwithsor_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B2C20nksrrotbh
sriwithsor_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B2C21nksrrotbh


SRR.Nokia.GSM.Operation_SMDeliveryStatus

SRR Operation measurements for SMDeliveryStatus operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
smdelivstatus_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B17C26nksrrotbh
smdelivstatus_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B17C16nksrrotbh
smdelivstatus_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B17C19nksrrotbh
smdelivstatus_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B17C18nksrrotbh
smdelivstatus_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B17C5nksrrotbh
smdelivstatus_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B17C2nksrrotbh
smdelivstatus_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B17C28nksrrotbh
smdelivstatus_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B17C24nksrrotbh
smdelivstatus_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B17C22nksrrotbh
smdelivstatus_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B17C23nksrrotbh
smdelivstatus_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B17C27nksrrotbh
smdelivstatus_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B17C6nksrrotbh
smdelivstatus_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B17C17nksrrotbh
smdelivstatus_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B17C25nksrrotbh
smdelivstatus_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B17C12nksrrotbh
smdelivstatus_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B17C13nksrrotbh
smdelivstatus_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B17C14nksrrotbh
smdelivstatus_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B17C15nksrrotbh
smdelivstatus_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B17C4nksrrotbh
smdelivstatus_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B17C8nksrrotbh
smdelivstatus_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B17C9nksrrotbh
smdelivstatus_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B17C10nksrrotbh
smdelivstatus_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B17C11nksrrotbh
smdelivstatus_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B17C3nksrrotbh
smdelivstatus_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B17C1nksrrotbh
smdelivstatus_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B17C7nksrrotbh
smdelivstatus_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B17C20nksrrotbh
smdelivstatus_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B17C21nksrrotbh


SRR.Nokia.GSM.Operation_Unknown

SRR Operation measurements for Unknown operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
unknownoperat_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B14C26nksrrotbh
unknownoperat_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B14C16nksrrotbh
unknownoperat_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B14C19nksrrotbh
unknownoperat_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B14C18nksrrotbh
unknownoperat_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B14C5nksrrotbh
unknownoperat_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B14C2nksrrotbh
unknownoperat_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B14C28nksrrotbh
unknownoperat_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B14C24nksrrotbh
unknownoperat_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B14C22nksrrotbh
unknownoperat_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B14C23nksrrotbh
unknownoperat_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B14C27nksrrotbh
unknownoperat_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B14C6nksrrotbh
unknownoperat_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B14C17nksrrotbh
unknownoperat_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B14C25nksrrotbh
unknownoperat_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B14C12nksrrotbh
unknownoperat_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B14C13nksrrotbh
unknownoperat_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B14C14nksrrotbh
unknownoperat_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B14C15nksrrotbh
unknownoperat_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B14C4nksrrotbh
unknownoperat_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B14C8nksrrotbh
unknownoperat_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B14C9nksrrotbh
unknownoperat_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B14C10nksrrotbh
unknownoperat_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B14C11nksrrotbh
unknownoperat_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B14C3nksrrotbh
unknownoperat_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B14C1nksrrotbh
unknownoperat_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B14C7nksrrotbh
unknownoperat_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B14C20nksrrotbh
unknownoperat_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B14C21nksrrotbh


SRR.Nokia.GSM.Operation_UpdateGPRSLocation

SRR Operation measurements for UpdateGPRSLocation operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
updategprsloc_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B11C26nksrrotbh
updategprsloc_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B11C16nksrrotbh
updategprsloc_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B11C19nksrrotbh
updategprsloc_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B11C18nksrrotbh
updategprsloc_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B11C5nksrrotbh
updategprsloc_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B11C2nksrrotbh
updategprsloc_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B11C28nksrrotbh
updategprsloc_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B11C24nksrrotbh
updategprsloc_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B11C22nksrrotbh
updategprsloc_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B11C23nksrrotbh
updategprsloc_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B11C27nksrrotbh
updategprsloc_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B11C6nksrrotbh
updategprsloc_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B11C17nksrrotbh
updategprsloc_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B11C25nksrrotbh
updategprsloc_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B11C12nksrrotbh
updategprsloc_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B11C13nksrrotbh
updategprsloc_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B11C14nksrrotbh
updategprsloc_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B11C15nksrrotbh
updategprsloc_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B11C4nksrrotbh
updategprsloc_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B11C8nksrrotbh
updategprsloc_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B11C9nksrrotbh
updategprsloc_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B11C10nksrrotbh
updategprsloc_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B11C11nksrrotbh
updategprsloc_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B11C3nksrrotbh
updategprsloc_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B11C1nksrrotbh
updategprsloc_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B11C7nksrrotbh
updategprsloc_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B11C20nksrrotbh
updategprsloc_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B11C21nksrrotbh


SRR.Nokia.GSM.Operation_UpdateLocation

SRR Operation measurements for UpdateLocation operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
updatelocatio_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B10C26nksrrotbh
updatelocatio_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B10C16nksrrotbh
updatelocatio_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B10C19nksrrotbh
updatelocatio_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B10C18nksrrotbh
updatelocatio_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B10C5nksrrotbh
updatelocatio_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B10C2nksrrotbh
updatelocatio_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B10C28nksrrotbh
updatelocatio_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B10C24nksrrotbh
updatelocatio_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B10C22nksrrotbh
updatelocatio_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B10C23nksrrotbh
updatelocatio_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B10C27nksrrotbh
updatelocatio_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B10C6nksrrotbh
updatelocatio_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B10C17nksrrotbh
updatelocatio_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B10C25nksrrotbh
updatelocatio_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B10C12nksrrotbh
updatelocatio_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B10C13nksrrotbh
updatelocatio_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B10C14nksrrotbh
updatelocatio_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B10C15nksrrotbh
updatelocatio_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B10C4nksrrotbh
updatelocatio_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B10C8nksrrotbh
updatelocatio_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B10C9nksrrotbh
updatelocatio_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B10C10nksrrotbh
updatelocatio_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B10C11nksrrotbh
updatelocatio_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B10C3nksrrotbh
updatelocatio_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B10C1nksrrotbh
updatelocatio_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B10C7nksrrotbh
updatelocatio_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B10C20nksrrotbh
updatelocatio_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B10C21nksrrotbh


SRR.Nokia.GSM.Operation_USSD_Notify

SRR Operation measurements for USSD Notify operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ussdnotify_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B7C26nksrrotbh
ussdnotify_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B7C16nksrrotbh
ussdnotify_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B7C19nksrrotbh
ussdnotify_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B7C18nksrrotbh
ussdnotify_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B7C5nksrrotbh
ussdnotify_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B7C2nksrrotbh
ussdnotify_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B7C28nksrrotbh
ussdnotify_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B7C24nksrrotbh
ussdnotify_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B7C22nksrrotbh
ussdnotify_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B7C23nksrrotbh
ussdnotify_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B7C27nksrrotbh
ussdnotify_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B7C6nksrrotbh
ussdnotify_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B7C17nksrrotbh
ussdnotify_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B7C25nksrrotbh
ussdnotify_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B7C12nksrrotbh
ussdnotify_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B7C13nksrrotbh
ussdnotify_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B7C14nksrrotbh
ussdnotify_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B7C15nksrrotbh
ussdnotify_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B7C4nksrrotbh
ussdnotify_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B7C8nksrrotbh
ussdnotify_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B7C9nksrrotbh
ussdnotify_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B7C10nksrrotbh
ussdnotify_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B7C11nksrrotbh
ussdnotify_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B7C3nksrrotbh
ussdnotify_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B7C1nksrrotbh
ussdnotify_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B7C7nksrrotbh
ussdnotify_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B7C20nksrrotbh
ussdnotify_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B7C21nksrrotbh


SRR.Nokia.GSM.Operation_USSD_Request

SRR Operation measurements for USSD Request operations. There is a secondary key of Direction Network Identifier.

The performance data measurements for this KPI group are recorded against the combination of SRR and DNI (dni_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ussdrequest_capacitylimitACCUMULATIONINT8Error: The number portability database has returned error status indicating that predefined capacity is exceeded.SRRM.M320B8C26nksrrotbh
ussdrequest_categorbarredACCUMULATIONINT8Error: Subscribers number portability category is barredSRRM.M320B8C16nksrrotbh
ussdrequest_cdpabarredACCUMULATIONINT8Error: Called party address is barred based on CdPA analysisSRRM.M320B8C19nksrrotbh
ussdrequest_cgpabarredACCUMULATIONINT8Error: Calling party address is barred based on CgPA analysisSRRM.M320B8C18nksrrotbh
ussdrequest_frngnotknwnprACCUMULATIONINT8Success: A foreign national number not known to be ported.SRRM.M320B8C5nksrrotbh
ussdrequest_frngprtd3rdneACCUMULATIONINT8Success: Aforeign national number ported to another foreign national networkSRRM.M320B8C2nksrrotbh
ussdrequest_internalerrorACCUMULATIONINT8Error: Used for internal errors and can be, for example: no response from number portability database, configuration error in number portability database.SRRM.M320B8C28nksrrotbh
ussdrequest_invalidmapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with MAP operations can be one of the following: decoding problems at TCAP user level (both MAP an INAP), service key in InitialDP does not indicate supported service logic, MSISDN parameter is missing from operation.SRRM.M320B8C24nksrrotbh
ussdrequest_invalidsccpACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of the invalid data at SCCP level.SRRM.M320B8C22nksrrotbh
ussdrequest_invalidtcapACCUMULATIONINT8Error: An incoming signalling message cannot be handled because of invalid data in it. Problems with TC dialogue and component handling primitivesSRRM.M320B8C23nksrrotbh
ussdrequest_loopACCUMULATIONINT8Error: Relay functionality cannot be performed because of (possible) loop.SRRM.M320B8C27nksrrotbh
ussdrequest_numberchangedACCUMULATIONINT8Success: number translation has been performed to the original number according to primary routing info in the number portability database.SRRM.M320B8C6nksrrotbh
ussdrequest_operatibarredACCUMULATIONINT8Error: Operation code specific data was set to barred in the operation code specific dat fileSRRM.M320B8C17nksrrotbh
ussdrequest_overloadACCUMULATIONINT8Error: An incoming operation is rejected because there are overload situations in SRR. Overload can occur in the number portability database or in the signalling unit.SRRM.M320B8C25nksrrotbh
ussdrequest_ownnumber2ACCUMULATIONINT8Success: An own number not ported out 2SRRM.M320B8C12nksrrotbh
ussdrequest_ownnumber3ACCUMULATIONINT8Success: An own number not ported out 3SRRM.M320B8C13nksrrotbh
ussdrequest_ownnumber4ACCUMULATIONINT8Success: An own number not ported out 4SRRM.M320B8C14nksrrotbh
ussdrequest_ownnumber5ACCUMULATIONINT8Success: An own number not ported out 5SRRM.M320B8C15nksrrotbh
ussdrequest_ownnumberACCUMULATIONINT8Success: An own number not ported outSRRM.M320B8C4nksrrotbh
ussdrequest_portedin2ACCUMULATIONINT8Success: A foreign national number ported in 2.SRRM.M320B8C8nksrrotbh
ussdrequest_portedin3ACCUMULATIONINT8Success: A foreign national number ported in 3.SRRM.M320B8C9nksrrotbh
ussdrequest_portedin4ACCUMULATIONINT8Success: A foreign national number ported in 4.SRRM.M320B8C10nksrrotbh
ussdrequest_portedin5ACCUMULATIONINT8Success: A foreign national number ported in 5.SRRM.M320B8C11nksrrotbh
ussdrequest_portedinACCUMULATIONINT8Success: A foreign national number ported in.SRRM.M320B8C3nksrrotbh
ussdrequest_portedoutACCUMULATIONINT8Success: An own number ported out.SRRM.M320B8C1nksrrotbh
ussdrequest_subseqprtdACCUMULATIONINT8Success: Subscriber who has not originally been an own subscriber can be handled as subsequently ported. If the porting status is subsequently ported, a message can go out with a prefix even if it came in with a prefixSRRM.M320B8C7nksrrotbh
ussdrequest_unknownsubscrACCUMULATIONINT8Error: Number portability database does not know the subscriberSRRM.M320B8C20nksrrotbh
ussdrequest_vernotsupportACCUMULATIONINT8Error: MAP application terminating function (MATF) handling is needed for the incoming MAP message but the version of the dialogue is too high, not supported.SRRM.M320B8C21nksrrotbh


SRR.Nokia.GSM.Rejected_Calls

This section describes the counters of M114

KPITypeData TypeDescriptionDerivationAdditional Summaries
rej_error_foundINTENSITYINTEGERTag appears at the end of the given counter group with field value 244 if an unexpected error situation has occurred.REJSRR.M114B2C13nksrrotbh
rej_exchg_inc_percentx10INTENSITYFLOATThe ticket service rejection percentage (0.0...100.0) of all the signalling units of the exchange regardless of the computer units that have been under observation.REJSRR.M114B2C7nksrrotbh
rej_exchg_incACCUMULATIONINT8The total sum of rejected incoming service requests (0...999999999) at the ticket service of all the signaling units of the exchange regardless of the computer units that have been under observation.REJSRR.M114B2C6nksrrotbh
rej_exchg_outgoingACCUMULATIONINT8The number of rejected service requests (0...999999999) that have exceeded the higher rejection limit of the message buffer on the outgoing side. The number of rejected service requests that have exceeded the higher rejection limit of the CPU load on the incoming side.REJSRR.M114B2C8nksrrotbh
rej_no_resp_from_lrmproINTENSITYINTEGERTag appears at the end of the given counter group with field value 242 if the signaling unit has not sent the required information for the following exchange-related counters: REJ_EXCHG_INC, REJ_EXCHG_INC_PERCENT*10, REJ_EXCHG_OUTGOING.REJSRR.M114B2C10nksrrotbh
rej_no_resp_from_signprbINTENSITYINTEGERTag appears at the end of the given counter group with field value 243 if the required information has not been received from the signalling process family that provides counters of the measured object.REJSRR.M114B2C11nksrrotbh
rej_observ_restartedINTENSITYINTEGERTag appears at the end of the given counter group with field value 16 if the signalling unit has not responded during the previous results accumulation period. Therefore, the observation has been restarted during the current results accumulation period. The counters is printed out during the following period.REJSRR.M114B2C12nksrrotbh
rej_report_inquiry_failINTENSITYINTEGERTag appears at the end of the given counter group with field value 241 if only part of the required information is received from the signalling process family that provides the counters of the measured object.REJSRR.M114B2C9nksrrotbh


SRR.Nokia.GSM.SCCP_Single_Meter

This table contains measurement data of one or more signalling networks.

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_hop_counterACCUMULATIONINT8Hop counter violationSINSRR.M219B2C16nksrrotbh
rea_err_failACCUMULATIONINT8Reassembly error - Reassembly failedSINSRR.M219B2C13nksrrotbh
rea_err_segmentACCUMULATIONINT8Reassembly error - Segment received out of sequenceSINSRR.M219B2C11nksrrotbh
rea_err_spaceACCUMULATIONINT8Reassembly error - No reassembly spaceSINSRR.M219B2C12nksrrotbh
rea_err_timer_expiryACCUMULATIONINT8Reassembly error - Timer T(reass) expirySINSRR.M219B2C10nksrrotbh
sccp_from_localACCUMULATIONINT8Processed SCCP messages from a local subsystem.SINSRR.M219B2C2nksrrotbh
sccp_to_localACCUMULATIONINT8Processed SCCP messages to a local subsystem.SINSRR.M219B2C1nksrrotbh
sccp_totalACCUMULATIONINT8Processed SCCP messages, totalSINSRR.M219B2C5nksrrotbh
sccp_userACCUMULATIONINT8Processed users independent SCCP messages.SINSRR.M219B2C4nksrrotbh
seg_err_failACCUMULATIONINT8Segmentation error - Segmentation failedSINSRR.M219B2C15nksrrotbh
seg_err_no_supportACCUMULATIONINT8Segmentation error - Segmenting not SupportedSINSRR.M219B2C14nksrrotbh
stp_gtACCUMULATIONINT8STP messages requiring GT translation.SINSRR.M219B2C8nksrrotbh
stpACCUMULATIONINT8Processed STP messagesSINSRR.M219B2C3nksrrotbh
with_gt_from_localACCUMULATIONINT8Messages requiring GT translation from a local subsystem.SINSRR.M219B2C7nksrrotbh
with_gt_to_localACCUMULATIONINT8Messages requiring GT translation to a local subsystem.SINSRR.M219B2C6nksrrotbh
with_gt_totalACCUMULATIONINT8Messages requiring GT translation, totalSINSRR.M219B2C9nksrrotbh


SRR.Nokia.GSM.SCCP_Subsystem_Local_Availability

This measurement contains measurement data of one or more signalling networks. N.B. There is a secondary key of signalling_network

The performance data measurements for this KPI group are recorded against the combination of SRR and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
dura_of_local_sccp_unavailableACCUMULATIONINT8Duration of the unavailability of a local SCCPLOCSRR.M218B2C5nksrrotbh
start_time_sccp_busyACCUMULATIONINT8Start of unavailability of a local SCCP due to maintenance busyLOCSRR.M218B2C2nksrrotbh
start_time_sccp_congACCUMULATIONINT8Start of unavailability of a local SCCP due to congestionLOCSRR.M218B2C3nksrrotbh
start_time_sccp_failACCUMULATIONINT8Start of unavailability of a local SCCP due to failureLOCSRR.M218B2C1nksrrotbh
stop_time_sccpACCUMULATIONINT8Stop of unavailability of a local SCCPLOCSRR.M218B2C4nksrrotbh


SRR.Nokia.GSM.SCCP_Subsystem

This measurement contains measurement data of one or more SCCP subsystems.N.B. There is a secondary key of signalling_network and of subsystem

The performance data measurements for this KPI group are recorded against the combination of SRR, Signalling_Network (signalling_network_id) and Subsystem (subsystem_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
csm_accepted_localACCUMULATIONINT8Acceptance of a coordinated state modification request by a local subsystemSUBSRR.M217B2C1nksrrotbh
csm_accepted_remoteACCUMULATIONINT8Acceptance of a coordinated state modification request by a remote subsystemSUBSRR.M217B2C2nksrrotbh
csm_rejected_localACCUMULATIONINT8Rejection of a coordinated state modification request by a local subsystemSUBSRR.M217B2C3nksrrotbh
csm_rejected_remoteACCUMULATIONINT8Rejection of a coordinated state modification request by a remote subsystemSUBSRR.M217B2C4nksrrotbh
dt1_receivedACCUMULATIONINT8DT 1 messages received from MTP per sink SSNSUBSRR.M217B2C15nksrrotbh
dt1_transACCUMULATIONINT8DT 1 messages sent to MTP per source SSNSUBSRR.M217B2C16nksrrotbh
dt2_receivedACCUMULATIONINT8DT 2 messages received from MTP per sink SSNSUBSRR.M217B2C17nksrrotbh
dt2_transACCUMULATIONINT8DT 2 messages sent to MTP per source SSNSUBSRR.M217B2C18nksrrotbh
ed_receivedACCUMULATIONINT8ED messages received from MTP per sink SSNSUBSRR.M217B2C19nksrrotbh
ed_transACCUMULATIONINT8ED messages sent to MTP per source SSNSUBSRR.M217B2C20nksrrotbh
err_segmentationACCUMULATIONINT8Messages too large for segmentationSUBSRR.M217B2C23nksrrotbh
msg_all_localACCUMULATIONINT8All messages related to a local subsystemSUBSRR.M217B2C9nksrrotbh
msg_from_local_with_gtACCUMULATIONINT8Messages addressed from a local subsystem that require GT translationSUBSRR.M217B2C8nksrrotbh
msg_from_local_without_gtACCUMULATIONINT8Messages addressed from a local subsystem that do not require GT translationSUBSRR.M217B2C7nksrrotbh
msg_received_class0ACCUMULATIONINT8All received messages in protocol class 0SUBSRR.M217B2C13nksrrotbh
msg_received_class1ACCUMULATIONINT8All received messages in protocol class 1SUBSRR.M217B2C14nksrrotbh
msg_redundantACCUMULATIONINT8All messages transmitted to the redundant subsystemSUBSRR.M217B2C10nksrrotbh
msg_to_local_with_gtACCUMULATIONINT8Messages addressed to a local subsystem that require GT translationSUBSRR.M217B2C6nksrrotbh
msg_to_local_withou_gtACCUMULATIONINT8Messages addressed to a local subsystem that do not require GT translationSUBSRR.M217B2C5nksrrotbh
msg_trans_class0ACCUMULATIONINT8All transmitted messages in protocol class 0SUBSRR.M217B2C11nksrrotbh
msg_trans_class1ACCUMULATIONINT8All transmitted messages in protocol class 1SUBSRR.M217B2C12nksrrotbh
prohibited_start_timeACCUMULATIONINT8Start of local subsystem prohibitedSUBSRR.M217B2C21nksrrotbh
prohibited_stop_timeACCUMULATIONINT8Stop of local subsystem prohibitedSUBSRR.M217B2C22nksrrotbh


SRR.Nokia.GSM.Security_Report

This measurement contains the results of the security counter measurement. The measurement collects information about the system from the security point of view. N.B. There is a secondary key of security_counter

The performance data measurements for this KPI group are recorded against the combination of SRR and Security_Counter (security_counter_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
critical_limitACCUMULATIONINT8Critical limit is not set for successful events. The operator cannot set a critical limit for this counter.RSEC.M176B17C2nksrrotbh
lo_term_count_reset_ddINTENSITYINTEGERCounter gives the day of long term counters reset time.RSEC.M176B0C4nksrrotbh
lo_term_count_reset_hourINTENSITYINTEGERCounter gives the hours of long term counters reset time.RSEC.M176B0C5nksrrotbh
lo_term_count_reset_minINTENSITYINTEGERCounter gives the minutes of long term counters reset time.RSEC.M176B0C6nksrrotbh
lo_term_count_reset_mmINTENSITYINTEGERCounter gives the month of long term counters reset time.RSEC.M176B0C3nksrrotbh
lo_term_count_reset_secINTENSITYINTEGERCounter gives the seconds of long term counters reset time.RSEC.M176B0C7nksrrotbh
lo_term_count_reset_yyINTENSITYINTEGERCounter gives the year of long term counters reset time.RSEC.M176B0C2nksrrotbh
long_term_totalACCUMULATIONINT8This counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B17C3nksrrotbh
reason_for_reportINTENSITYINTEGERCounter gives a value which tells the reason for report. 1 = PERIODICAL, 2 = OUTPUT TIME CHANGED, 3 = CRITICAL LIMIT, 4 = OPERATORRSEC.M176B0C1nksrrotbh
sec_critical_limit_10INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B10C2nksrrotbh
sec_critical_limit_11INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B11C2nksrrotbh
sec_critical_limit_12INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B12C2nksrrotbh
sec_critical_limit_13INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B13C2nksrrotbh
sec_critical_limit_14INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B14C2nksrrotbh
sec_critical_limit_15INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B15C2nksrrotbh
sec_critical_limit_16INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B16C2nksrrotbh
sec_critical_limit_1INTENSITYINTEGERCritical limit is not set for successful events. The operator cannot set a critical limit for this counter.RSEC.M176B1C2nksrrotbh
sec_critical_limit_2INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B2C2nksrrotbh
sec_critical_limit_3INTENSITYINTEGERCritical limit is not set for successful events. The operator cannot set a critical limit for this counter.RSEC.M176B3C2nksrrotbh
sec_critical_limit_4INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B4C2nksrrotbh
sec_critical_limit_5INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B5C2nksrrotbh
sec_critical_limit_6INTENSITYINTEGERCritical limit is not set for successful events. The operator cannot set a critical limit for this counter.RSEC.M176B6C2nksrrotbh
sec_critical_limit_7INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B7C2nksrrotbh
sec_critical_limit_8INTENSITYINTEGERCounter shows the alarm limit for the security counter. When the counter reaches the value or a multiple of the value shown in this field, alarm 1569 is generated.RSEC.M176B8C2nksrrotbh
sec_critical_limit_9INTENSITYINTEGERCritical limit is not set for creating new users. The operator cannot set a critical limit for this counter.RSEC.M176B9C2nksrrotbh
sec_long_term_total_10ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B10C3nksrrotbh
sec_long_term_total_11ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B11C3nksrrotbh
sec_long_term_total_12ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B12C3nksrrotbh
sec_long_term_total_13ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B13C3nksrrotbh
sec_long_term_total_14ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B14C3nksrrotbh
sec_long_term_total_15ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B15C3nksrrotbh
sec_long_term_total_16ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B16C3nksrrotbh
sec_long_term_total_1ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B1C3nksrrotbh
sec_long_term_total_2ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B2C3nksrrotbh
sec_long_term_total_3ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B3C3nksrrotbh
sec_long_term_total_4ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B4C3nksrrotbh
sec_long_term_total_5ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B5C3nksrrotbh
sec_long_term_total_6ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B6C3nksrrotbh
sec_long_term_total_7ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B7C3nksrrotbh
sec_long_term_total_8ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B8C3nksrrotbh
sec_long_term_total_9ACCUMULATIONINT8Counter shows the total number of events during the period from the previous reset of the long-term counters to the output time.RSEC.M176B9C3nksrrotbh
sec_total_10ACCUMULATIONINT8Counter shows the total number of log writing failures during the reporting period.RSEC.M176B10C1nksrrotbh
sec_total_11ACCUMULATIONINT8Counter shows the total number of command check errors during the reporting period.RSEC.M176B11C1nksrrotbh
sec_total_12ACCUMULATIONINT8Counter shows the total number of authentication failures during the reporting period.RSEC.M176B12C1nksrrotbh
sec_total_13ACCUMULATIONINT8Counter shows the total number of unknown IMSI numbers during the reporting period.RSEC.M176B13C1nksrrotbh
sec_total_14ACCUMULATIONINT8Counter shows the total number of IMEI numbers found to be on the black list during the reporting period.RSEC.M176B14C1nksrrotbh
sec_total_15ACCUMULATIONINT8Counter shows the total number of IMEI numbers found to be on the grey list during the reporting period.RSEC.M176B15C1nksrrotbh
sec_total_16ACCUMULATIONINT8Counter shows the total number of unknown IMEI numbers during the reporting period.RSEC.M176B16C1nksrrotbh
sec_total_1ACCUMULATIONINT8Counter shows the total number of successful events during the reporting period.RSEC.M176B1C1nksrrotbh
sec_total_2ACCUMULATIONINT8Counter shows the total number of illegal login attempts during the reporting period.RSEC.M176B2C1nksrrotbh
sec_total_3ACCUMULATIONINT8Counter shows the total number of successful events during the reporting period.RSEC.M176B3C1nksrrotbh
sec_total_4ACCUMULATIONINT8Counter shows the total number of attempts to access a network element with an invalid username or password during the reporting period.RSEC.M176B4C1nksrrotbh
sec_total_5ACCUMULATIONINT8Counter shows the total number of attempts to access a network element with inadequate access rights during the reporting period.RSEC.M176B5C1nksrrotbh
sec_total_6ACCUMULATIONINT8Counter shows the total number of started MML sessions during the reporting period.RSEC.M176B6C1nksrrotbh
sec_total_7ACCUMULATIONINT8Counter shows the total number of attempts to open an MML session with an invalid username or password during the reporting period.RSEC.M176B7C1nksrrotbh
sec_total_8ACCUMULATIONINT8Counter shows the total number of attempts to give MML commands with inadequate access rights during the reporting period.RSEC.M176B8C1nksrrotbh
sec_total_9ACCUMULATIONINT8Counter shows the total number of new usernames that have been created during the reporting period.RSEC.M176B9C1nksrrotbh
totalACCUMULATIONINT8This counter shows the total number of successful events during the reporting period.RSEC.M176B17C1nksrrotbh


SRR.Nokia.GSM.SRR_Signalling_Pt_Traffic_User

Signalling traffic measurements

The performance data measurements for this KPI group are recorded against the combination of SRR, SIO (sio_id) and Signalling_Network (signalling_network_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
sif_sio_receivedACCUMULATIONINT8The number of SIF and SIO received with the given SIO.UTRASRR.M214B2C1 
sif_sio_transACCUMULATIONINT8The number of SIF and SIO transmitted with the given SIO.UTRASRR.M214B2C2 


SRR.Nokia.GSM.Support_Service_Long

The SRR support service measures the incoming and outgoing SRRi service operations per operation code.N.B. There is a secondary key of SRR_service

The performance data measurements for this KPI group are recorded against the combination of SRR and SRR_Service (srr_service_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
li_initialdp_accesdeniedACCUMULATIONINT8Long, Incoming, InitialDP (INAP), General, Access is deniedSRRSSP.M344B21011C2nksrrotbh
li_initialdp_aservsetfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, AService set number foundSRRSSP.M344B21012C3nksrrotbh
li_initialdp_aservsetnotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, AService set number not foundSRRSSP.M344B21012C4nksrrotbh
li_initialdp_avalidfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, AValidation number foundSRRSSP.M344B21012C1nksrrotbh
li_initialdp_avalidnotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, AValidation number not foundSRRSSP.M344B21012C2nksrrotbh
li_initialdp_avalwserfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, AValidation with service set number foundSRRSSP.M344B21012C7nksrrotbh
li_initialdp_avalwsernotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, AValidation with service set number not foundSRRSSP.M344B21012C8nksrrotbh
li_initialdp_bservsetfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, BService set number foundSRRSSP.M344B21012C5nksrrotbh
li_initialdp_bservsetnotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, BService set number not foundSRRSSP.M344B21012C6nksrrotbh
li_initialdp_insystarifffndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, IN-System tariff information foundSRRSSP.M344B21012C11nksrrotbh
li_initialdp_insystarnotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, IN-System tariff information not foundSRRSSP.M344B21012C12nksrrotbh
li_initialdp_reroutianotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, Rerouting based A-number number not foundSRRSSP.M344B21012C10nksrrotbh
li_initialdp_reroutingafndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), Service, Rerouting based A-number number foundSRRSSP.M344B21012C9nksrrotbh
li_initialdp_skeynotfndACCUMULATIONINT8Long, Incoming, InitialDP (INAP), General, Service key not foundSRRSSP.M344B21011C1nksrrotbh
li_initialdpcap_accesdeniedACCUMULATIONINT8Long, Incoming, InitialDP (CAP), General, Access is deniedSRRSSP.M344B21021C2nksrrotbh
li_initialdpcap_aservsetfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, AService set number foundSRRSSP.M344B21022C3nksrrotbh
li_initialdpcap_aservsetnotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, AService set number not foundSRRSSP.M344B21022C4nksrrotbh
li_initialdpcap_avalidfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, AValidation number foundSRRSSP.M344B21022C1nksrrotbh
li_initialdpcap_avalidnotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, AValidation number not foundSRRSSP.M344B21022C2nksrrotbh
li_initialdpcap_avalwserfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, AValidation with service set number foundSRRSSP.M344B21022C7nksrrotbh
li_initialdpcap_avalwsernotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, AValidation with service set number not foundSRRSSP.M344B21022C8nksrrotbh
li_initialdpcap_bservsetfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, BService set number foundSRRSSP.M344B21022C5nksrrotbh
li_initialdpcap_bservsetnotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, BService set number not foundSRRSSP.M344B21022C6nksrrotbh
li_initialdpcap_insystarifffndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, IN-System tariff information foundSRRSSP.M344B21022C11nksrrotbh
li_initialdpcap_insystarnotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, IN-System tariff information not foundSRRSSP.M344B21022C12nksrrotbh
li_initialdpcap_reroutianotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, Rerouting based A-number number not foundSRRSSP.M344B21022C10nksrrotbh
li_initialdpcap_reroutingafndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), Service, Rerouting based A-number number foundSRRSSP.M344B21022C9nksrrotbh
li_initialdpcap_skeynotfndACCUMULATIONINT8Long, Incoming, InitialDP (CAP), General, Service key not foundSRRSSP.M344B21021C1nksrrotbh
lo_initialdp_insystarifffndACCUMULATIONINT8Long, Outgoing, InitialDP (INAP), Service, IN-System tariff information foundSRRSSP.M344B22012C11nksrrotbh
lo_initialdpcap_insystarifffndACCUMULATIONINT8Long, Outgoing, InitialDP (CAP), Service, IN-System tariff information foundSRRSSP.M344B22022C11nksrrotbh


SRR.Nokia.GSM.Support_Service_Short

The SRR support service measures the incoming and outgoing SRRi service operations per operation code. N.B. There is a secondary key of SRR_service

The performance data measurements for this KPI group are recorded against the combination of SRR and SRR_Service (srr_service_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
si_initialdp_accesdeniedACCUMULATIONINT8Short, Incoming, InitialDP (INAP), General, Access is deniedSRRSSP.M344B11011C2nksrrotbh
si_initialdp_aservsetfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, A-Service set number foundSRRSSP.M344B11012C3nksrrotbh
si_initialdp_aservsetnotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, A-Service set number not foundSRRSSP.M344B11012C4nksrrotbh
si_initialdp_avalidfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, A-Validation number foundSRRSSP.M344B11012C1nksrrotbh
si_initialdp_avalidnotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, A-Validation number not foundSRRSSP.M344B11012C2nksrrotbh
si_initialdp_avalwserfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, A-Validation with service set number foundSRRSSP.M344B11012C7nksrrotbh
si_initialdp_avalwsernotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, A-Validation with service set number not foundSRRSSP.M344B11012C8nksrrotbh
si_initialdp_bservsetfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, B-Service set number foundSRRSSP.M344B11012C5nksrrotbh
si_initialdp_bservsetnotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, B-Service set number not foundSRRSSP.M344B11012C6nksrrotbh
si_initialdp_insystarifffndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, IN-System tariff information foundSRRSSP.M344B11012C11nksrrotbh
si_initialdp_insystarnotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, IN-System tariff information not foundSRRSSP.M344B11012C12nksrrotbh
si_initialdp_reroutianotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, Rerouting based A-number number not foundSRRSSP.M344B11012C10nksrrotbh
si_initialdp_reroutingafndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), Service, Rerouting based A-number number foundSRRSSP.M344B11012C9nksrrotbh
si_initialdp_skeynotfndACCUMULATIONINT8Short, Incoming, InitialDP (INAP), General, Service key not foundSRRSSP.M344B11011C1nksrrotbh
si_initialdpcap_accesdeniedACCUMULATIONINT8Short, Incoming, InitialDP (CAP), General, Access is deniedSRRSSP.M344B11021C2nksrrotbh
si_initialdpcap_aservsetfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, AService set number foundSRRSSP.M344B11022C3nksrrotbh
si_initialdpcap_aservsetnotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, AService set number foundSRRSSP.M344B11022C4nksrrotbh
si_initialdpcap_avalidfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, AValidation number foundSRRSSP.M344B11022C1nksrrotbh
si_initialdpcap_avalidnotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, AValidation number not foundSRRSSP.M344B11022C2nksrrotbh
si_initialdpcap_avalwserfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, AValidation with service set number foundSRRSSP.M344B11022C7nksrrotbh
si_initialdpcap_avalwsernotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, AValidation with service set number not foundSRRSSP.M344B11022C8nksrrotbh
si_initialdpcap_bservsetfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, BService set number foundSRRSSP.M344B11022C5nksrrotbh
si_initialdpcap_bservsetnotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, BService set number not foundSRRSSP.M344B11022C6nksrrotbh
si_initialdpcap_insystarifffndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, IN-System tariff information foundSRRSSP.M344B11022C11nksrrotbh
si_initialdpcap_insystarnotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, IN-System tariff information not foundSRRSSP.M344B11022C12nksrrotbh
si_initialdpcap_reroutianotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, Rerouting based A-number number not foundSRRSSP.M344B11022C10nksrrotbh
si_initialdpcap_reroutingafndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), Service, Rerouting based A-number number foundSRRSSP.M344B11022C9nksrrotbh
si_initialdpcap_skeynotfndACCUMULATIONINT8Short, Incoming, InitialDP (CAP), General, Service key not foundSRRSSP.M344B11021C1nksrrotbh
so_initialdp_insystarifffndACCUMULATIONINT8Short, Outgoing, InitialDP (INAP), Service, IN-System tariff information foundSRRSSP.M344B12012C11nksrrotbh
so_initialdpcap_insystarifffndACCUMULATIONINT8Short, Outgoing, InitialDP (CAP), Service, IN-System tariff information foundSRRSSP.M344B12022C11nksrrotbh


SRR.Nokia.GSM.TCAP_Messages

This table contains measurement data of one or more signalling links in the transaction capabilities application part.Related to messages

KPITypeData TypeDescriptionDerivationAdditional Summaries
msg_discardedACCUMULATIONINT8The number of messages discardedTCAPSRR.M220B5C2nksrrotbh
received_abortACCUMULATIONINT8The number of received ABORT messagesTCAPSRR.M220B6C10nksrrotbh
received_beginACCUMULATIONINT8The number of received BEGIN messagesTCAPSRR.M220B6C4nksrrotbh
received_continueACCUMULATIONINT8The number of received CONTINUE messagesTCAPSRR.M220B6C6nksrrotbh
received_endACCUMULATIONINT8The number of received END messagesTCAPSRR.M220B6C8nksrrotbh
received_unidirectionalACCUMULATIONINT8The number of received UNIDIRECTIONAL messagesTCAPSRR.M220B6C2nksrrotbh
tc_total_receivedACCUMULATIONINT8The number of received UNIDIRECTIONAL messagesTCAPSRR.M220B6C12nksrrotbh
tc_total_transACCUMULATIONINT8The number of transmitted UNIDIRECTIONAL messagesTCAPSRR.M220B6C11nksrrotbh
trans_abortACCUMULATIONINT8The number of transmitted ABORT messagesTCAPSRR.M220B6C9nksrrotbh
trans_beginACCUMULATIONINT8The number of transmitted BEGIN messagesTCAPSRR.M220B6C3nksrrotbh
trans_continueACCUMULATIONINT8The number of transmitted CONTINUE messagesTCAPSRR.M220B6C5nksrrotbh
trans_endACCUMULATIONINT8The number of transmitted END messagesTCAPSRR.M220B6C7nksrrotbh
trans_unidirectionalACCUMULATIONINT8The number of transmitted UNIDIRECTIONAL messagesTCAPSRR.M220B6C1nksrrotbh


SRR.Nokia.GSM.TCAP_Performance

This table contains measurement data of one or more signalling links in the transaction capabilities application part.

KPITypeData TypeDescriptionDerivationAdditional Summaries
err_transactionACCUMULATIONINT8The number of errors detected in the transaction portionTCAPSRR.M220B5C5nksrrotbh
pa_receivedACCUMULATIONINT8The number of provider aborts receivedTCAPSRR.M220B5C3nksrrotbh
received_tc_componentsACCUMULATIONINT8The number of received TC componentsTCAPSRR.M220B6C14nksrrotbh
rej_receivedACCUMULATIONINT8The number of rejects receivedTCAPSRR.M220B5C4nksrrotbh
tcl_cancelACCUMULATIONINT8The number of received TCL cancel indications for class 1 operationsTCAPSRR.M220B5C1nksrrotbh
trans_tc_componentsACCUMULATIONINT8The number of transmitted TC componentsTCAPSRR.M220B6C13nksrrotbh


SRR.Nokia.GSM.TCAP_Protocol_Error_In_Completion_Portion

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to protocol errors in the completion portion.

KPITypeData TypeDescriptionDerivationAdditional Summaries
comp_received_bad_structureACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: badly structured componentTCAPSRR.M220B3C5nksrrotbh
comp_received_mistypedACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: mistyped componentTCAPSRR.M220B3C3nksrrotbh
comp_received_ret_errorACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: return error unexpectedTCAPSRR.M220B3C15nksrrotbh
comp_received_ret_resultACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: return result unexpectedTCAPSRR.M220B3C11nksrrotbh
comp_received_unrecognizedACCUMULATIONINT8Protocol error in completion portion (reject rec.) problem code: unrecognised componentTCAPSRR.M220B3C1nksrrotbh
comp_trans_bad_structureACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: badly structured componentTCAPSRR.M220B3C6nksrrotbh
comp_trans_mistypedACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: mistyped componentTCAPSRR.M220B3C4nksrrotbh
comp_trans_ret_errorACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: return error unexpectedTCAPSRR.M220B3C16nksrrotbh
comp_trans_unrecognizedACCUMULATIONINT8Protocol error in completion portion (reject sent.) problem code: unrecognised componentTCAPSRR.M220B3C2nksrrotbh
reject_rxed_unrec_invoke_id_reACCUMULATIONINT8Protocol error in comp. portion (reject rec.)-problem code: unrecognized invoke id. (RE)TCAPSRR.M220B3C13nksrrotbh
reject_rxed_unrec_invoke_id_rrACCUMULATIONINT8Protocol error in comp. portion (reject rec.)- problem code: unrecognized invoke id. (RR)TCAPSRR.M220B3C9nksrrotbh
reject_rxed_unrec_linked_idACCUMULATIONINT8Protocol error in comp. portion (reject rec.)- problem code: unrecognized linked id. TCAPSRR.M220B3C7nksrrotbh
reject_sent_return_result_unexACCUMULATIONINT8Protocol error in comp. portion (reject sent)-problem code: return result unexpected TCAPSRR.M220B3C12nksrrotbh
reject_sent_unrec_invoke_id_reACCUMULATIONINT8Protocol error in comp. portion (reject sent)- problem code: unrecognized invoke id. (RE)TCAPSRR.M220B3C14nksrrotbh
reject_sent_unrec_invoke_id_rrACCUMULATIONINT8Protocol error in comp. portion (reject sent)-problem code: unrecognized invoke id. (RR)TCAPSRR.M220B3C10nksrrotbh
reject_sent_unrec_linked_idACCUMULATIONINT8Protocol error in comp. portion (reject sent)- problem code: unrecognized linked idTCAPSRR.M220B3C8nksrrotbh


SRR.Nokia.GSM.TCAP_Protocol_Error_Transaction_Portion

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to errors in the transaction portion

KPITypeData TypeDescriptionDerivationAdditional Summaries
ab_received_msg_typeACCUMULATIONINT8Protocol error in transaction portion (abort received) - unrecognised message typeTCAPSRR.M220B2C1nksrrotbh
ab_received_rlimitACCUMULATIONINT8Protocol error in transaction portion (abort received) - resource limitationTCAPSRR.M220B2C9nksrrotbh
ab_received_ta_bad_formatACCUMULATIONINT8Protocol error in transaction portion (abort received) - badly formatted transaction portionTCAPSRR.M220B2C5nksrrotbh
ab_received_ta_incorrectACCUMULATIONINT8Protocol error in transaction portion (abort received) - incorrect transaction portionTCAPSRR.M220B2C3nksrrotbh
ab_trans_msg_typeACCUMULATIONINT8Protocol error in transaction portion (abort sent) - unrecognised message typeTCAPSRR.M220B2C2nksrrotbh
ab_trans_rlimitACCUMULATIONINT8Protocol error in transaction portion (abort sent) - resource limitationTCAPSRR.M220B2C10nksrrotbh
ab_trans_ta_bad_formatACCUMULATIONINT8Protocol error in transaction portion (abort sent) - badly formatted transaction portionTCAPSRR.M220B2C6nksrrotbh
ab_trans_ta_incorrectACCUMULATIONINT8Protocol error in transaction portion (abort sent) - incorrect transaction portionTCAPSRR.M220B2C4nksrrotbh
abort_rxed_unrec_transact_idACCUMULATIONINT8Protocol error in transaction portion ( abort received ) - unrecognized transaction identifier( 14.1d in ITU-T Q.752 )TCAPSRR.M220B2C7nksrrotbh
abort_sent_unrec_transact_idACCUMULATIONINT8Protocol error in transaction portion ( abort sent ) - unrecognized transaction identifier (14.4d in ITU-T Q.752)TCAPSRR.M220B2C8nksrrotbh


SRR.Nokia.GSM.TCAP_Transaction

This section describes the TC transactions meters measurement.N.B. There is a secondary key of signalling_network and subsystem

The performance data measurements for this KPI group are recorded against the combination of SRR, Signalling_Network (snet_id) and Subsystem (ssn_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
max_openINTENSITYINTEGERMaximum number of open transaction Ids during the periodTTRASRR.M224B2C4nksrrotbh
mean_durationACCUMULATIONINT8Cumulative mean duration of transactionsTTRASRR.M224B2C3nksrrotbh
newACCUMULATIONINT8The number of new transactions during the periodTTRASRR.M224B2C1nksrrotbh
openINTENSITYFLOATMean number of open transaction Ids during the periodTTRASRR.M224B2C2nksrrotbh


SRR.Nokia.GSM.TCAP_User_Generated_Problems

This table contains measurement data of one or more signalling links in the transaction capabilities application part. Related to user generated problems

KPITypeData TypeDescriptionDerivationAdditional Summaries
reject_rxed_duplic_invoke_idACCUMULATIONINT8TC user generated problem (Reject received) - duplicate invoke id. ( 14.3a in ITU-T Q.752 )TCAPSRR.M220B4C1nksrrotbh
reject_sent_duplic_invoke_idACCUMULATIONINT8TC user generated problem (Reject sent) -duplicate invoke id. ( 14.6a in ITU-T Q.752 )TCAPSRR.M220B4C2nksrrotbh
tc_received_init_releaseACCUMULATIONINT8TC user generated problem (reject rec.) problem code: initiating releaseTCAPSRR.M220B4C9nksrrotbh
tc_received_link_op_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unexpected link operationTCAPSRR.M220B4C13nksrrotbh
tc_received_link_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: link response unexpectedTCAPSRR.M220B4C11nksrrotbh
tc_received_mistyped_paramACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameterTCAPSRR.M220B4C5nksrrotbh
tc_received_mistyped_reACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameter (RE)TCAPSRR.M220B4C21nksrrotbh
tc_received_mistyped_rrACCUMULATIONINT8TC user generated problem (reject rec.) problem code: mistyped parameter (RR)TCAPSRR.M220B4C19nksrrotbh
tc_received_rlimitACCUMULATIONINT8TC user generated problem (reject rec.) problem code: resource limitationTCAPSRR.M220B4C7nksrrotbh
tc_received_unexpectACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unexpected errorTCAPSRR.M220B4C17nksrrotbh
tc_received_unknown_opACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unrecognised operationTCAPSRR.M220B4C3nksrrotbh
tc_received_unrecognizedACCUMULATIONINT8TC user generated problem (reject rec.) problem code: unrecognised errorTCAPSRR.M220B4C15nksrrotbh
tc_trans_init_releaseACCUMULATIONINT8TC user generated problem (reject sent.) problem code: initiating releaseTCAPSRR.M220B4C10nksrrotbh
tc_trans_link_op_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unexpected link operationTCAPSRR.M220B4C14nksrrotbh
tc_trans_link_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: link response unexpectedTCAPSRR.M220B4C12nksrrotbh
tc_trans_mistyped_paramACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameterTCAPSRR.M220B4C6nksrrotbh
tc_trans_mistyped_reACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameter (RE)TCAPSRR.M220B4C22nksrrotbh
tc_trans_mistyped_rrACCUMULATIONINT8TC user generated problem (reject sent.) problem code: mistyped parameter (RR)TCAPSRR.M220B4C20nksrrotbh
tc_trans_rlimitACCUMULATIONINT8TC user generated problem (reject sent.) problem code: resource limitationTCAPSRR.M220B4C8nksrrotbh
tc_trans_unexpectACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unexpected errorTCAPSRR.M220B4C18nksrrotbh
tc_trans_unknown_opACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unrecognised operationTCAPSRR.M220B4C4nksrrotbh
tc_trans_unrecognizedACCUMULATIONINT8TC user generated problem (reject sent.) problem code: unrecognised errorTCAPSRR.M220B4C16nksrrotbh


STM1_Set Performance Indicators

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


STM1_Set.Nokia.GSM.Far_End

far end counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
FE_MUX_BBEACCUMULATIONINT8Multiplex section background block errors at the far end. An errored block is a block in which one or more bits have an error. M1 byte conveys the count of errored blocks which is calculated by the far end from its receiving blocks by using B2 bytes at multiplexer level. B2 bytes are the bytes allocated for a multiplex section error monitoring function, which is Bit Interleaved Parity 24 (BIP-24) code using even parity. The BIP-24 is computed over all bits of the previous STM frame, excluding RSOH and placed in byte B2 of the current frame. In this case the block means STM-1 frame.The counter is incremented when one or more bit errors are detected in a block (STM-1 frame excluding the RSOH). The counter is not updated during SES and UAS conditions.STM1.M513B3C7 
FE_MUX_ESACCUMULATIONINT8Multiplex section errored second at the far end. This shows the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval, the contents of the counters are obtained by the relevant managed objects. The objects are multiplex section (M1) errors and MS-RDI. In this case the block means STM-1 frame.The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B3C8 
FE_MUX_SESACCUMULATIONINT8Shows multiplex section severely errored seconds at the far end. The number of one second periods which contain errored blocks more or equal to the threshold or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are multiplex section (M1) errors and MS-RDI. In this case the block means STM-1 frame. During SES condition also counter FE_MUX_ES M513B3C8 is incremented.The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect. The counter is not updated during the UAS condition.STM1.M513B3C9 
FE_MUX_UASACCUMULATIONINT8The multiplex section unavailable seconds at the Far End.A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are part of the available time.The counter is updated after ten consecutive SES events are detected. These ten seconds are included in the counter. The update of the counter is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B3C6 
FE_PATH1_BBEACCUMULATIONINT8The path termination section background block errors at the far end.An errored block is a block in which one or more bits have an error. G1 byte in the Section Overhead Header (SOH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-3 or VC-4 according to the configuration) and is placed in byte B3 of the current frame. In this case the block means virtual container. The counter is updated when one or more bit errors are detected in a block (virtual container). The counter is not updated during the SES and UAS conditions.STM1.M513B4C7 
FE_PATH1_ESACCUMULATIONINT8The path termination section errored seconds at the far end.The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are path termination section (G1) errors and HP-RDI. In this case the block means virtual container. The counter is updated when a second contains one or more errored blocks, or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C8 
FE_PATH1_SESACCUMULATIONINT8The path termination section severely errored seconds at the far end.The number of one second periods which contain errored blocks more or equal to that in the threshold, or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP-RDI. In this case the block means virtual container. During the SES condition the FE_PATH1_ES (M513B4C8) counter is also updated. The counter is updated when a second contains errored blocks more or equal to that in the defined threshold, or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C9 
FE_PATH1_UASACCUMULATIONINT8Path termination section shows unavailable seconds at the far end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time.The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. The counter update is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B4C6 
FE_PATH2_BBEACCUMULATIONINT8Shows Path termination section background block errors at the far end. An errored block is a block in which one or more bits have an error. G1 byte in the section overhead header (SOH) is used for monitoring path termination section error, by using Bit Interleaved Parity 8 (BIP-8) code in an even parity. The BIP-8 is computed over all bits of the previous virtual container (VC-3 or VC-4 according to configuration) and is placed in byte B3 of the current frame. In this case the block means virtual container.The counter is incremented when one or more bit errors are detected in a block (virtual container). The counter is not updated during the SES and UAS conditions.STM1.M513B4C15 
FE_PATH2_ESACCUMULATIONINT8Path termination section errored seconds at the far end. It shows the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP-RDI. In this case the block means virtual container. The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C16 
FE_PATH2_SESACCUMULATIONINT8Path termination section severely errored seconds at the far end.The number of one second periods which contain errored blocks more than or equal to that in the threshold, or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP- RDI. In this case the block means virtual container. During the SES condition FE_PATH2_ES (M513B4C16) counter is also updated.The counter is updated when a second contains errored blocks more or equal to that in the defined threshold, or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C17 
FE_PATH2_UASACCUMULATIONINT8Path termination section shows unavailable seconds at the far end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time. The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. The counter update is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B4C14 
FE_PATH3_BBEACCUMULATIONINT8Path termination section background block errors at the far end.An errored block is a block in which one or more bits have an error. G1 byte in the Section Overhead Header (SOH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-3 or VC-4 according to the configuration) and is placed in byte B3 of the current frame. In this case the block means virtual container. The counter is updated when one or more bit errors are detected in a block (virtual container). The counter is not updated during the SES and UAS conditions.STM1.M513B4C23 
FE_PATH3_ESACCUMULATIONINT8Path termination section errored seconds at the far end.The number of seconds with one or more errored blocks, or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP-RDI. In this case the block means virtual container.The counter is updated when a second contains one or more errored blocks, or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C24 
FE_PATH3_SESACCUMULATIONINT8Path termination section severely errored seconds at the far end. It shows the number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP-RDI. In this case the block means virtual container. The path termination section is one of the SDH layers (regeneration, multiplex and path) (ITU-T G.707). During the SES condition counter FE_PATH3_ES M513B4C24 is also incremented. The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold, or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C25 
FE_PATH3_UASACCUMULATIONINT8Shows path termination section unavailable seconds at the far end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time. The counter is updated when ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B4C22 


STM1_Set.Nokia.GSM.Near_End

Near end counters

KPITypeData TypeDescriptionDerivationAdditional Summaries
NE_MUX_BBEACCUMULATIONINT8Shows multiplex section background block errors at the near end. An errored block is a block in which one or more bits have an error. B2 byte in the section overhead header (SOH) is used for multiplex section error monitoring by using Bit Interleaved Parity 24 (BIP-24) code in an even parity. The BIP-24 is computed over all the bits of the previous STM frame, excluding RSOH, and it is placed in byte B2 of the current frame before scrambling. In this case the block means STM-1 frame. The counter is incremented when one or more bit errors are detected in a block (STM-1 frame, excluding RSOH).The counter is not updated during the SES and UAS conditions.STM1.M513B3C3 
NE_MUX_ESACCUMULATIONINT8Shows multiplex section errored seconds at the near end.It shows the number of seconds with one or more errored blocks, or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are multiplex section (B2) errors and MS-AIS.The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B3C4 
NE_MUX_SESACCUMULATIONINT8Shows multiplex section severely errored seconds at the near end. It shows the number of one second periods which contain errored blocks more or equal to that in the defined threshold errored blocks, or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are multiplex section (B2) errors and MS-AIS. In this case the block means STM-1 frame. During the SES condition, counter NE_MUX_ES M513B3C4 is also incremented. The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold, or at least one defect. The counter is not updated during the UAS condition.STM1.M513B3C5 
NE_MUX_UASACCUMULATIONINT8Shows multiplex section unavailable seconds at the near end. A period of unavailable time begins at the start of ten consecutive SES events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non- SES events. These ten seconds are considered to be part of the available time. The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten consecutive non- SES events are detected. These ten seconds are not included in the counter.The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold, or at least one defect.STM1.M513B3C2 
NE_PATH1_BBEACCUMULATIONINT8Shows path termination section background block errors at the near end. An errored block is a block in which one or more bits have an error. B3 byte in the higher order path overhead header (HO-POH) is used for path termination section error monitoring, by using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-3 or VC-4 according to configuration) and it is placed in byte B3 of the current frame. In this case the block means virtual container. The counter is incremented when one or more bit errors are detected in a block (virtual container). The counter is not updated during the SES and UAS conditions.STM1.M513B4C3 
NE_PATH1_ESACCUMULATIONINT8Shows path termination section errored second at the near end. It shows the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container. The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C4 
NE_PATH1_SESACCUMULATIONINT8Shows path termination section severely errored seconds at the near end. It shows the number of one second periods which contain errored blocks, more or equal to that in the defined threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container. During the SES condition, counter NE_PATH1_ES M513B4C4 is also incremented.The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C5 
NE_PATH1_UASACCUMULATIONINT8Shows path termination section unavailable seconds at the near end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time. The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B4C2 
NE_PATH2_BBEACCUMULATIONINT8Shows path termination section background block errors at the near end. An errored block is a block in which one or more bits have an error. B3 byte in the higher order path overhead header (HO-POH) is used for monitoring path termination section errors, using Bit Interleaved Parity 8 (BIP-8) code in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-3 or VC-4 according to configuration) and it is placed in byte B3 of the current frame. In this case the block means virtual container.The counter is incremented when one or more bit errors are detected in a block (virtual container). The counter is not updated during the SES and UAS conditions.STM1.M513B4C11 
NE_PATH2_ESACCUMULATIONINT8Shows path termination section errored seconds at the near end. It shows the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container.The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C12 
NE_PATH2_SESACCUMULATIONINT8Shows path termination section severely errored seconds at the near end. It shows the number of one second periods which contain errored blocks more or equal to that in the defined threshold, or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container. During the SES condition, counter NE_PATH2_ES M513B4C12 is also incremented. The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C13 
NE_PATH2_UASACCUMULATIONINT8Shows path termination section unavailable seconds at the near end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time.The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B4C10 
NE_PATH3_BBEACCUMULATIONINT8Shows path termination section background block errors at the near end. An errored block is a block in which one or more bits have an error. B3 byte in the higher order path overhead header (HO-POH) is used for monitoring path termination section error, using Bit Interleaved Parity 8 (BIP-8) code in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-3 or VC-4 according to configuration) and is placed in byte B3 of the current frame. In this case the block means virtual container.The counter is incremented when one or more bit errors are detected in a block (virtual container). The counter is not updated during the SES and UAS conditions.STM1.M513B4C19 
NE_PATH3_ESACCUMULATIONINT8Shows path termination section errored seconds at the near end. It shows the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container. The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C20 
NE_PATH3_SESACCUMULATIONINT8Shows path termination section severely errored seconds at the near end. It shows the number of one second periods which contain errored blocks more or equal to that in the defined threshold, or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container. During the SES condition,counter NE_PATH3_ES M513B4C16 is also incremented.The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect. The counter is not updated during the UAS condition.STM1.M513B4C21 
NE_PATH3_UASACCUMULATIONINT8Shows path termination section unavailable seconds at the near end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time. The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B4C18 


STM1_Set.Nokia.GSM.Regenerator

STM1 regenerator stats

KPITypeData TypeDescriptionDerivationAdditional Summaries
REG_BBEACCUMULATIONINT8Shows regenerator section background block errors. An errored block is a block in which one or more bits have an error. B1 byte in the section overhead header (SOH) is used for monitoring regenerator section error, using the Bit Interleaved Parity 8 (BIP-8) code in an even parity. The BIP-8 is computed over all the bits of the previous STM frame after scrambling, and it is placed in byte B1 of the current frame before scrambling. In this case the block means STM-1 frame. The counter is incremented when one or more bit errors are detected in a block (STM-1 frame). The counter is not updated during the SES and UAS conditions.STM1.M513B2C3 
REG_ESACCUMULATIONINT8Shows regenerator section errored second. It shows the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the regeneration section (B1) errors and LOS or LOF events. In this case the block means STM-1 frame.The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.STM1.M513B2C4 
REG_SESACCUMULATIONINT8Shows regenerator section severely errored seconds. Is shows the number of one second periods which contain errored blocks more or equal to that in the defined threshold, or at least one defect. The threshold can be handled by the Exchange terminal configuration handling YANMML. The default value of the threshold is 30 %. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the regenerator section (B1) errors and regenerator section LOF/LOS events. In this case the block means STM-1 frame. The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect.STM1.M513B2C5 
REG_UASACCUMULATIONINT8Shows that the regenerator section is unavailable for a number of seconds (ITU-T G.826).The period of unavailable time begins at the start of ten consecutive severelyerrored second (SES) events. These ten seconds are considered to be part ofunavailable time. A new period of available time begins at the start of tenconsecutive non-SES events. These ten seconds are considered to be part ofavailable time. The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten consecutive non-SES events are detected. These ten seconds are not included in the counter.STM1.M513B2C2 


Timeslot Performance Indicators

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


Timeslot.Nokia.GSM.Circuit_Seizure_Supervision

Circuit seizure supervision measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
cise_state_0_free_ff_reserved2INTENSITYINTEGERState of the circuit (PCM-TSL) during the supervision period. Possible values: FREE (0) = the circuit has been free the whole of the supervision period RESERVED (255) = the circuit has been reserved the whole of the supervision period. Those circuits under circuit seizure supervision whose state has changed during the supervision period are not listed in the report.CRCDS.M144B2C3 
statusINTENSITYINTEGERCircuit status. 0 = circuit is not seized, -1 = circuit is seizedCRTSL.M144B2C3 


VLR Performance Indicators

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


VLR.Nokia.GSM.Authentication_Count

This table contains information about the AC measurement which shows the number of authentication triplets transferred from a specific HLR address.N.B. There is a secondary key of home_HLR

The performance data measurements for this KPI group are recorded against the combination of VLR and Number_Destination (DEST_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
nbr_ansACCUMULATIONINT8The number of successful answers received in response to the VLR authentication triplet request.ACVDEST.M86B3C4nkmtbh, nkvsubbh
nbr_not_answ_requestACCUMULATIONINT8The number of unanswered requests. ACVDEST.M86B3C21nkmtbh, nkvsubbh
nbr_quintetACCUMULATIONINT8The number of quintets. ACVDEST.M86B3C22nkmtbh, nkvsubbh
nbr_reqACCUMULATIONINT8The number of authentication triplet requests by the VLR.ACVDEST.M86B3C3nkmtbh, nkvsubbh
nbr_sync_requestACCUMULATIONINT8The number of synchronisation requests. ACVDEST.M86B3C20nkmtbh, nkvsubbh
nbr_triplACCUMULATIONINT8The number of transferred authentication triplets.ACVDEST.M86B3C6nkmtbh, nkvsubbh
nbr_unknownACCUMULATIONINT8The number of unknown subscribers whose data cannot be found in the AUC of the HLR.ACVDEST.M86B3C5nkmtbh, nkvsubbh
nweishlrifvalueis_1ACCUMULATIONINT8The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is HLR, which sent the authentication vector. In ASCII report appears HLR in NWE column.ACVDEST.M86B5C1nkmtbh, nkvsubbh
nweisplmnifvalueis_1ACCUMULATIONINT8The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is PLMN, which sent the authentication vector. In this case the HLR address of the subscriber is unknown and the VLR calculates the HLR address from IMSI. In ASCII report appears PLMN in NWE column.ACVDEST.M86B5C3nkmtbh, nkvsubbh
nweisvlrifvalueis_1ACCUMULATIONINT8The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is VLR, which sent the authentication vector. In ASCII report appears VLR in NWE column and the vectors came from the previous VLR after location update.ACVDEST.M86B5C2nkmtbh, nkvsubbh


VLR.Nokia.GSM.Authentication

This section describes the AC/VLR measurement.

KPITypeData TypeDescriptionDerivationAdditional Summaries
data_missing_in_tripletsACCUMULATIONINT8Data missing in triplet transfer counters ACVMSC.M86B4C3nkmtbh, nkvsubbh
nbr_attempt_auth_quintetACCUMULATIONINT8The number of authentication quintet attempts. ACVMSC.M86B2C8nkmtbh, nkvsubbh
nbr_attempt_auth_tripletACCUMULATIONINT8The number of authentication triplet attempts. ACVMSC.M86B2C7nkmtbh, nkvsubbh
nbr_nok_auth_quintetACCUMULATIONINT8The number of failed authentication quintets. ACVMSC.M86B2C4nkmtbh, nkvsubbh
nbr_nok_authACCUMULATIONINT8The number of failed authentications.ACVMSC.M86B2C2nkmtbh, nkvsubbh
nbr_of_vlrus_sent_dataACCUMULATIONINT8The number of VLRUs in the MSC that have sent data. ACVMSC.M86B4C2nkmtbh, nkvsubbh
nbr_of_vlrusACCUMULATIONINT8The number of VLRUs in the MS. ACVMSC.M86B4C1nkmtbh, nkvsubbh
nbr_ok_auth_quintetACCUMULATIONINT8The number of successful authentication quintets. ACVMSC.M86B2C3nkmtbh, nkvsubbh
nbr_ok_authACCUMULATIONINT8The number of successful authentications.ACVMSC.M86B2C1nkmtbh, nkvsubbh
nbr_reused_triplACCUMULATIONINT8The number of reused triplets.ACVMSC.M86B3C12nkmtbh, nkvsubbh
sync_fail_utms_subscACCUMULATIONINT8Synchronisation failure for UMTS subscribers.ACVMSC.M86B2C5nkmtbh, nkvsubbh
tot_nbr_ansACCUMULATIONINT8The total number of successful answers received in response to the VLR authentication triplet request.ACVMSC.M86B3C8nkmtbh, nkvsubbh
tot_nbr_not_answ_requestACCUMULATIONINT8The total number of unanswered requests. ACVMSC.M86B3C24nkmtbh, nkvsubbh
tot_nbr_quintetACCUMULATIONINT8The total number of quintets. ACVMSC.M86B3C25nkmtbh, nkvsubbh
tot_nbr_reqACCUMULATIONINT8The total number of authentication triplet requests of the VLR.ACVMSC.M86B3C7nkmtbh, nkvsubbh
tot_nbr_sync_requestACCUMULATIONINT8The total number of synchronisation requests. ACVMSC.M86B3C23nkmtbh, nkvsubbh
tot_nbr_triplACCUMULATIONINT8The total number of transferred authentication triplets.ACVMSC.M86B3C10nkmtbh, nkvsubbh
tot_nbr_unknownACCUMULATIONINT8The total number of unknown subscribers whose data cannot be found in the AUC of the HLR.ACVMSC.M86B3C9nkmtbh, nkvsubbh
user_reject_utms_subscACCUMULATIONINT8User rejected by UMTS subscribers.ACVMSC.M86B2C6nkmtbh, nkvsubbh


VLR.Nokia.GSM.HLR_Subscribers

This section describes the counters of M339: MeO MSC / DEST. N.B. There is a secondary key of home_HLR

The performance data measurements for this KPI group are recorded against the combination of VLR and Number_Destination (DEST_ID) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ave_subsc_home_hlrINTENSITYINTEGERThe average number of subscribers in the home HLRDESVLR.M339B2C5nkmtbh, nkvsubbh
cancel_locationACCUMULATIONINT8The number of CancelLocation operations received from the specific HLR. This counter is printed only with Feature 1627: Super-Charger feature.DESVLR.M339B2C6nkmtbh, nkvsubbh


VLR.Nokia.GSM.Idle_time

Idle time data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
activeaveidletimescINTENSITYFLOATIdle time for the DB cleaning represents the time passed between the deletion and the last activity of the active subscriber in minutes. Shows the average of the idle times during the measurement period. This counter is printed only with the superchargerVLR1MSC.M82B20C17nkmtbh, nkvsubbh
activemaxidletimescINTENSITYFLOATIdle time for the DB cleaning represents the time passed between the deletion and the last activity of the active subscriber in minutes. Shows the maximum of the idle times during the measurement period. This counter is printed only with the superchargerVLR1MSC.M82B20C18nkmtbh, nkvsubbh
activeminidletimescINTENSITYFLOATIdle time for the DB cleaning represents the time passed between the deletion and the last activity of the active subscriber in minutes. Shows the minimum of the idle times during the measurement period. This counter is printed only with the superchargerVLR1MSC.M82B20C16nkmtbh, nkvsubbh
aveidletimeclINTENSITYFLOATIdle time presents the time passed between the deletion and the last activity of the subscriber in minutes. Shows the average of the idle times during the measurement period. This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C7nkmtbh, nkvsubbh
maxidletimeclINTENSITYFLOATIdle time presents the time passed between the deletion and the last activity of the subscriber in minutes. Shows the maximum of the idle times during the measurement period. This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C8nkmtbh, nkvsubbh
minidletimeclINTENSITYFLOATIdle time presents the time passed between the deletion and the last activity of the subscriber in minutes. Shows the minimum of the idle times during the measurement period. This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C6nkmtbh, nkvsubbh
passiveaveidletimescINTENSITYFLOATIdle time for the DB cleaning represents the time passed between the deletion and the last activity of the passive subscriber in minutes. Shows the average of the idle times during the measurement period. This counter is printed only with the superchargerVLR1MSC.M82B20C20nkmtbh, nkvsubbh
passivemaxidletimescINTENSITYFLOATIdle time for the DB cleaning represents the time passed between the deletion and the last activity of the passive subscriber in minutes. Shows the maximum of the idle times during the measurement period. This counter is printed only with the superchargerVLR1MSC.M82B20C21nkmtbh, nkvsubbh
passiveminidletimescINTENSITYFLOATIdle time for the DB cleaning represents the time passed between the deletion and the last activity of the passive subscriber in minutes. Shows the minimum of the idle times during the measurement period. This counter is printed only with the superchargerVLR1MSC.M82B20C19nkmtbh, nkvsubbh
passtoactaveidletimescINTENSITYFLOATIdle time for the state changes represents the time passed between the actual state change (Passive to Active) and the last activity of the subscriber in minutes. Shows the average of the idle times during the measurement period. This counter is printed oVLR1MSC.M82B20C12nkmtbh, nkvsubbh
passtoactmaxidletimescINTENSITYFLOATIdle time for the state changes represents the time passed between the actual state change (Passive to Active) and the last activity of the subscriber in minutes. Shows the maximum of the idle times during the measurement period. This counter is printed oVLR1MSC.M82B20C13nkmtbh, nkvsubbh
passtoactminidletimescINTENSITYFLOATIdle time for the state changes represents the time passed between the actual state change (Passive to Active) and the last activity of the subscriber in minutes. Shows the minimum of the idle times during the measurement period. This counter is printed oVLR1MSC.M82B20C11nkmtbh, nkvsubbh


VLR.Nokia.GSM.Inter_VLR_GSM

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows Inter VLR measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_intervlrhsgsmsuccPERCENTAGEFLOATPercentage successful GSM location updates between VLRs performed by home subscriberspercentok({intervlrhsgsmsucc}, {intervlrhsgsmattempt})nkmtbh, nkvsubbh
%_intervlrrsgsmsuccPERCENTAGEFLOATPercentage successful GSM Location updates performed by visiting normal subscribers arriving from other PLMN or changing the VLR within the same PLMN.percentok({intervlrrsgsmsucc}, {intervlrrsgsmattempt})nkmtbh, nkvsubbh
intervlrhsgsmattemptACCUMULATIONINT8GSM location update attempts between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR). New home subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the ATTEMPT field both the normal and telemeteric subscribers are counted.VLR1MSC.M82B3C106nkmtbh, nkvsubbh
intervlrhsgsmsuccACCUMULATIONINT8GSM successful location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR). New home subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field only the normal subscribers are counted.VLR1MSC.M82B3C107nkmtbh, nkvsubbh
intervlrhsgsmsucctm1ACCUMULATIONINT8GSM location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR).VLR1MSC.M82B8C107nkmtbh, nkvsubbh
intervlrhsgsmsucctm2ACCUMULATIONINT8GSM location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR).VLR1MSC.M82B11C107nkmtbh, nkvsubbh
intervlrhsgsmsucctm3ACCUMULATIONINT8GSM location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR).VLR1MSC.M82B14C107nkmtbh, nkvsubbh
intervlrrsgsmattemptACCUMULATIONINT8GSM location update attempts performed by visiting normal subscribers arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM. In the ATTEMPT field both the normal and telemeteric subscribers are counted.VLR1MSC.M82B3C118nkmtbh, nkvsubbh
intervlrrsgsmsuccACCUMULATIONINT8GSM successful Location updates performed by visiting normal subscribers arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field only the normal subscribers are counted.VLR1MSC.M82B3C119nkmtbh, nkvsubbh
intervlrrsgsmsucctm1ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 1 arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM.VLR1MSC.M82B8C119nkmtbh, nkvsubbh
intervlrrsgsmsucctm2ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 2 arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIMVLR1MSC.M82B11C119nkmtbh, nkvsubbh
intervlrrsgsmsucctm3ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 3 arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM.VLR1MSC.M82B14C119nkmtbh, nkvsubbh


VLR.Nokia.GSM.Inter_VLR_UMTS

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows Inter VLR measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_inter_vlr_hs_umts_succPERCENTAGEFLOATPercentage successful UMTS location updates between VLRs performed by home subscriberspercentok({inter_vlr_hs_umts_succ}, {inter_vlr_hs_umts_attempt})nkmtbh, nkvsubbh
%_inter_vlr_rs_umts_succPERCENTAGEFLOATPercentage successfulpercentok({inter_vlr_rs_umts_succ}, {inter_vlr_rs_umts_attempt})nkmtbh, nkvsubbh
inter_vlr_hs_umts_attemptACCUMULATIONINT8UMTS location update attempts between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR). New home subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the ATTEMPT field both the normal and telemeteric subscribers are counted.VLR1MSC.M82B3C108nkmtbh, nkvsubbh
inter_vlr_hs_umts_succtm1ACCUMULATIONINT8UMTS location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR).VLR1MSC.M82B8C109nkmtbh, nkvsubbh
inter_vlr_hs_umts_succtm2ACCUMULATIONINT8UMTS location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR).VLR1MSC.M82B11C109nkmtbh, nkvsubbh
inter_vlr_hs_umts_succtm3ACCUMULATIONINT8UMTS location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR).VLR1MSC.M82B14C109nkmtbh, nkvsubbh
inter_vlr_hs_umts_succACCUMULATIONINT8UMTS successful location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR). New home subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field only the normal subscribers are countedVLR1MSC.M82B3C109nkmtbh, nkvsubbh
inter_vlr_rs_umts_attemptACCUMULATIONINT8UMTS location update attempts performed by visiting normal subscribers arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM. In the ATTEMPT field both the normal and telemeteric subscribers are counted.VLR1MSC.M82B3C120nkmtbh, nkvsubbh
inter_vlr_rs_umts_succtm1ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 1 arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM.VLR1MSC.M82B8C121nkmtbh, nkvsubbh
inter_vlr_rs_umts_succtm2ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 2 arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM.VLR1MSC.M82B11C121nkmtbh, nkvsubbh
inter_vlr_rs_umts_succtm3ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 3 arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM.VLR1MSC.M82B14C121nkmtbh, nkvsubbh
inter_vlr_rs_umts_succACCUMULATIONINT8UMTS successful Location updates performed by visiting normal subscribers arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field only the normal subscribers are counted.VLR1MSC.M82B3C121nkmtbh, nkvsubbh


VLR.Nokia.GSM.Intra_VLR_GSM

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows Intra VLR measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_intravlrinterplmnhsgsmsuccPERCENTAGEFLOATPercentage successful GSM location updates between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.percentok({intravlrinterplmnhsgsmsucc}, {intravlrinterplmnhsgsmattempt})nkmtbh, nkvsubbh
%_intravlrinterplmnrsgsmsuccPERCENTAGEFLOATPercentage succesfulGSM location updates performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.percentok({intravlrinterplmnrsgsmsucc}, {intravlrinterplmnrsgsmattempt})nkmtbh, nkvsubbh
%_intravlrintraplmnhsgsmsuccPERCENTAGEFLOATPercentage successful GSM location updates between location areas made by home normal subscribers inside the VLR and within the same PLMN.percentok({intravlrintraplmnhsgsmsucc}, {intravlrintraplmnhsgsmattempt})nkmtbh, nkvsubbh
%_intravlrintraplmnrsgsmsuccPERCENTAGEFLOATPercentage successful GSM Location updates performed by visiting normal subscribers inside the VLR and within the same PLMN.percentok({intravlrintraplmnrsgsmsucc}, {intravlrintraplmnrsgsmattempt})nkmtbh, nkvsubbh
intravlriaplmnhsgsmattempttm1ACCUMULATIONINT8GSM location update attempts between location areas made by home telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C101nkmtbh, nkvsubbh
intravlriaplmnhsgsmattempttm2ACCUMULATIONINT8GSM location update attempts between location areas made by home telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C101nkmtbh, nkvsubbh
intravlriaplmnhsgsmattempttm3ACCUMULATIONINT8GSM location update attempts between location areas made by home telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C101nkmtbh, nkvsubbh
intravlriaplmnhsgsmsucctm1ACCUMULATIONINT8GSM successful location updates between location areas made by home telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C102nkmtbh, nkvsubbh
intravlriaplmnhsgsmsucctm2ACCUMULATIONINT8GSM successful location updates between location areas made by home telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C102nkmtbh, nkvsubbh
intravlriaplmnhsgsmsucctm3ACCUMULATIONINT8GSM successful location updates between location areas made by home telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C102nkmtbh, nkvsubbh
intravlriaplmnrsgsmattempttm1ACCUMULATIONINT8GSM location update attempts performed by visiting telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C110nkmtbh, nkvsubbh
intravlriaplmnrsgsmattempttm2ACCUMULATIONINT8GSM location update attempts performed by visiting telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C110nkmtbh, nkvsubbh
intravlriaplmnrsgsmattempttm3ACCUMULATIONINT8GSM location update attempts performed by visiting telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C110nkmtbh, nkvsubbh
intravlriaplmnrsgsmsucctm1ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C111nkmtbh, nkvsubbh
intravlriaplmnrsgsmsucctm2ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C111nkmtbh, nkvsubbh
intravlriaplmnrsgsmsucctm3ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C111nkmtbh, nkvsubbh
intravlrieplmnhsgsmattempttm1ACCUMULATIONINT8GSM location update attempts between location areas made by home telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B8C105nkmtbh, nkvsubbh
intravlrieplmnhsgsmattempttm2ACCUMULATIONINT8GSM location update attempts between location areas made by home telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B11C105nkmtbh, nkvsubbh
intravlrieplmnhsgsmattempttm3ACCUMULATIONINT8GSM location update attempts between location areas made by home telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B14C105nkmtbh, nkvsubbh
intravlrieplmnhsgsmsucctm1ACCUMULATIONINT8GSM successful location updates between location areas made by home telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B8C131nkmtbh, nkvsubbh
intravlrieplmnhsgsmsucctm2ACCUMULATIONINT8GSM successful location updates between location areas made by home telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B11C131nkmtbh, nkvsubbh
intravlrieplmnhsgsmsucctm3ACCUMULATIONINT8GSM successful location updates between location areas made by home telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B14C131nkmtbh, nkvsubbh
intravlrieplmnrsgsmattempttm1ACCUMULATIONINT8GSM location update attempts performed by visiting telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B8C114nkmtbh, nkvsubbh
intravlrieplmnrsgsmattempttm2ACCUMULATIONINT8GSM location update attempts performed by visiting telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B11C114nkmtbh, nkvsubbh
intravlrieplmnrsgsmattempttm3ACCUMULATIONINT8GSM location update attempts performed by visiting telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B14C114nkmtbh, nkvsubbh
intravlrieplmnrsgsmsucctm1ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B8C115nkmtbh, nkvsubbh
intravlrieplmnrsgsmsucctm2ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B11C115nkmtbh, nkvsubbh
intravlrieplmnrsgsmsucctm3ACCUMULATIONINT8GSM successful location updates performed by visiting telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B14C115nkmtbh, nkvsubbh
intravlrinterplmnhsgsmattemptACCUMULATIONINT8GSM location update attempts between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C105nkmtbh, nkvsubbh
intravlrinterplmnhsgsmsuccACCUMULATIONINT8GSM successful location updates between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C131nkmtbh, nkvsubbh
intravlrinterplmnrsgsmattemptACCUMULATIONINT8GSM location update attempts performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C114nkmtbh, nkvsubbh
intravlrinterplmnrsgsmsuccACCUMULATIONINT8GSM successful location updates performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C115nkmtbh, nkvsubbh
intravlrintraplmnhsgsmattemptACCUMULATIONINT8GSM location update attempts between location areas made by home normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C101nkmtbh, nkvsubbh
intravlrintraplmnhsgsmsuccACCUMULATIONINT8GSM successful location updates between location areas made by home normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C102nkmtbh, nkvsubbh
intravlrintraplmnrsgsmattemptACCUMULATIONINT8GSM location update attempts performed by visiting normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C110nkmtbh, nkvsubbh
intravlrintraplmnrsgsmsuccACCUMULATIONINT8GSM successful Location updates performed by visiting normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C111nkmtbh, nkvsubbh


VLR.Nokia.GSM.Intra_VLR_UMTS

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows Intra VLR measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_intra_vlr_inter_plmn_hs_umts_succPERCENTAGEFLOATPercentage successful UMTS location updates between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.percentok({intra_vlr_inter_plmn_hs_umts_succ}, {intra_vlr_inter_plmn_hs_umts_attempt})nkmtbh, nkvsubbh
%_intra_vlr_inter_plmn_rs_umts_succPERCENTAGEFLOATPercentage successful UMTS location updates performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.percentok({intra_vlr_inter_plmn_rs_umts_succ}, {intra_vlr_inter_plmn_rs_umts_attempt})nkmtbh, nkvsubbh
%_intra_vlr_intra_plmn_rs_umts_succPERCENTAGEFLOATPercentage successful UMTS location updates performed by visiting normal subscribers inside the VLR and within the same PLMN.percentok({intra_vlr_intra_plmn_rs_umts_succ}, {intra_vlr_intra_plmn_rs_umts_attempt})nkmtbh, nkvsubbh
%_intravlrintraplmnhsumtssuccPERCENTAGEFLOATPercentage successful UMTS location updates between location areas made by home normal subscribers inside the VLR and within the same PLMN.percentok({intravlrintraplmnhsumtssucc}, {intravlrintraplmnhsumtsattempt})nkmtbh, nkvsubbh
intra_vlr_ia_plmn_hs_umts_attempttm1ACCUMULATIONINT8UMTS location update attempts between location areas made by home telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C103nkmtbh, nkvsubbh
intra_vlr_ia_plmn_hs_umts_attempttm2ACCUMULATIONINT8UMTS location update attempts between location areas made by home telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C103nkmtbh, nkvsubbh
intra_vlr_ia_plmn_hs_umts_attempttm3ACCUMULATIONINT8UMTS location update attempts between location areas made by home telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C103nkmtbh, nkvsubbh
intra_vlr_ia_plmn_hs_umts_succtm1ACCUMULATIONINT8UMTS successful location updates between location areas made by home telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C104nkmtbh, nkvsubbh
intra_vlr_ia_plmn_hs_umts_succtm2ACCUMULATIONINT8UMTS successful location updates between location areas made by home telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C104nkmtbh, nkvsubbh
intra_vlr_ia_plmn_hs_umts_succtm3ACCUMULATIONINT8UMTS successful location updates between location areas made by home telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C104nkmtbh, nkvsubbh
intra_vlr_ia_plmn_rs_umts_attempttm1ACCUMULATIONINT8UMTS location update attempts performed by visiting telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C112nkmtbh, nkvsubbh
intra_vlr_ia_plmn_rs_umts_attempttm2ACCUMULATIONINT8UMTS location update attempts performed by visiting telemeteric subscribers category 2 inside the VLR and within the same PLMN.VLR1MSC.M82B11C112nkmtbh, nkvsubbh
intra_vlr_ia_plmn_rs_umts_attempttm3ACCUMULATIONINT8UMTS location update attempts performed by visiting telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C112nkmtbh, nkvsubbh
intra_vlr_ia_plmn_rs_umts_succtm1ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 1 inside the VLR and within the same PLMN.VLR1MSC.M82B8C113nkmtbh, nkvsubbh
intra_vlr_ia_plmn_rs_umts_succtm2ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 2 inside the VLR and within the same PLMNVLR1MSC.M82B11C113nkmtbh, nkvsubbh
intra_vlr_ia_plmn_rs_umts_succtm3ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 3 inside the VLR and within the same PLMN.VLR1MSC.M82B14C113nkmtbh, nkvsubbh
intra_vlr_ie_plmn_hs_umts_attempttm1ACCUMULATIONINT8UMTS location update attempts between location areas made by home telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B8C132nkmtbh, nkvsubbh
intra_vlr_ie_plmn_hs_umts_attempttm2ACCUMULATIONINT8UMTS location update attempts between location areas made by home telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B11C132nkmtbh, nkvsubbh
intra_vlr_ie_plmn_hs_umts_succtm1ACCUMULATIONINT8UMTS successful location updates between location areas made by home telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B8C133nkmtbh, nkvsubbh
intra_vlr_ie_plmn_hs_umts_succtm2ACCUMULATIONINT8UMTS successful location updates between location areas made by home telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B11C133nkmtbh, nkvsubbh
intra_vlr_ie_plmn_rs_umts_attempttm1ACCUMULATIONINT8UMTS location update attempts performed by visiting telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B8C116nkmtbh, nkvsubbh
intra_vlr_ie_plmn_rs_umts_attempttm2ACCUMULATIONINT8UMTS location update attempts performed by visiting telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B11C116nkmtbh, nkvsubbh
intra_vlr_ie_plmn_rs_umts_attempttm3ACCUMULATIONINT8UMTS location update attempts performed by visiting telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B14C116nkmtbh, nkvsubbh
intra_vlr_ie_plmn_rs_umts_succtm1ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 1 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B8C117nkmtbh, nkvsubbh
intra_vlr_ie_plmn_rs_umts_succtm2ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 2 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B11C117nkmtbh, nkvsubbh
intra_vlr_ie_plmn_rs_umts_succtm3ACCUMULATIONINT8UMTS successful location updates performed by visiting telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B14C117nkmtbh, nkvsubbh
intra_vlr_inter_plmn_hs_umts_attemptACCUMULATIONINT8UMTS location update attempts between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C132nkmtbh, nkvsubbh
intra_vlr_inter_plmn_hs_umts_succACCUMULATIONINT8UMTS successful location updates between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C133nkmtbh, nkvsubbh
intra_vlr_inter_plmn_rs_umts_attemptACCUMULATIONINT8UMTS location update attempts performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C116nkmtbh, nkvsubbh
intra_vlr_inter_plmn_rs_umts_succACCUMULATIONINT8UMTS successful location updates performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs.VLR1MSC.M82B3C117nkmtbh, nkvsubbh
intra_vlr_intra_plmn_rs_umts_attemptACCUMULATIONINT8UMTS location update attempts performed by visiting normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C112nkmtbh, nkvsubbh
intra_vlr_intra_plmn_rs_umts_succACCUMULATIONINT8UMTS successful location updates performed by visiting normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C113nkmtbh, nkvsubbh
intravlrieplmnhsumtsattempttm3ACCUMULATIONINT8UMTS location update attempts between location areas made by home telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B14C132nkmtbh, nkvsubbh
intravlrieplmnhsumtssucctm3ACCUMULATIONINT8UMTS successful location updates between location areas made by home telemeteric subscribers category 3 inside the VLR but the original and target location areas belong to different PLMNsVLR1MSC.M82B14C133nkmtbh, nkvsubbh
intravlrintraplmnhsumtsattemptACCUMULATIONINT8UMTS location update attempts between location areas made by home normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C103nkmtbh, nkvsubbh
intravlrintraplmnhsumtssuccACCUMULATIONINT8UMTS successful location updates between location areas made by home normal subscribers inside the VLR and within the same PLMN.VLR1MSC.M82B3C104nkmtbh, nkvsubbh


VLR.Nokia.GSM.PLMN_Subscribers

This measurement contains the average number of subscribers per PLMN in the VLR measurement.N.B. There is a secondary key of PLMN

The performance data measurements for this KPI group are recorded against the combination of VLR and PLMN (plmn_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
ave_subsc_plmnINTENSITYINTEGERThe average number of subscribers in the visitor PLMNPLMNV.M340B2C3nkmtbh, nkvsubbh
cancel_locationACCUMULATIONINT8The number of CancelLocation operations received from the specific home PLMN. This counter is printed only with Feature 1627: Super-Charger.PLMNV.M340B2C4nkmtbh, nkvsubbh
data_missing_in_subsc_valuesACCUMULATIONINT8This line is printed if data transfer from one or several VLRUs failed during one or more inquiries, that is, only a subset of the data could be collected. It means that the printed subscriber numbers per PLMN are not reliable. (The problem can be overloaded VLRUs, a VLRU startup.) CODING: BytePLMNV.M340B2C1nkmtbh, nkvsubbh
send_idACCUMULATIONINT8The number of Send Identity operations received from the specific home PLMN. This counter is printed only with Feature 1627: Super-Charger.PLMNV.M340B2C5nkmtbh, nkvsubbh


VLR.Nokia.GSM.PSI_Prepaging

PSI Prepaging

KPITypeData TypeDescriptionDerivationAdditional Summaries
PSI_PREPAGING_CS_DOMAIN_ATTACCUMULATIONINT8These counters should be used for pre-paging when the paging attempt is sent via Iu or A interface.VLR1MSC.M82B24C5nkmtbh
PSI_PREPAGING_CS_DOMAIN_SUCCACCUMULATIONINT8These counters should be used for successful pre-paging when the paging is sent via Iu or A interface.VLR1MSC.M82B24C6nkmtbh
PSI_PREPAGING_MS_SEARCH_ATTACCUMULATIONINT8The search attempts done through all A and Iu interface and Serving GPRS Support NodesVLR1MSC.M82B24C1nkmtbh
PSI_PREPAGING_MS_SEARCH_SUCCACCUMULATIONINT8The successful search attempts done through all A and Iu interface and Serving GPRS Support NodesVLR1MSC.M82B24C2nkmtbh
PSI_PREPAGING_PS_DOMAIN_ATTACCUMULATIONINT8The pre-paging attempts done through SGSN.VLR1MSC.M82B24C7nkmtbh
PSI_PREPAGING_PS_DOMAIN_SUCCACCUMULATIONINT8The successful pre-pagings done through SGSN.VLR1MSC.M82B24C8nkmtbh
PSI_PREPAGING_SUBSCRIBER_BUSYACCUMULATIONINT8The number of pre-pagings (both CS and PS domain) and searchings when the subscriber is busy.VLR1MSC.M82B24C9nkmtbh
PSI_PREPGN_MS_S_ATT_NBR_FAILACCUMULATIONINT8The number of pre-paging requests sent to A and Iu interface (from the MSC) during the measurement period when the paging result has failed.VLR1MSC.M82B24C4nkmtbh
PSI_PREPGN_MS_S_ATT_NBR_SUCCACCUMULATIONINT8The number of pre-paging requests sent to A and Iu interface (from the MSC) during the measurement period when the paging result is successful.VLR1MSC.M82B24C3nkmtbh


VLR.Nokia.GSM.SPC_Authentication_Count

This section describes the key columns and counters of M86: MeO MSC / SPC.N.B. There is a secondary key of signalling_point

The performance data measurements for this KPI group are recorded against the combination of VLR and Signalling_Point (signalling_point_id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
nbr_quintetACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) The number of quintets. obsolete.obsoletenkmtbh, nkvsubbh
numberofansweredACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) Number of successful answers received to the VLR authentication vector requests obsolete.obsoletenkmtbh, nkvsubbh
numberofnotansweredACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) Number of not answered authentication vector requests.obsolete.obsoletenkmtbh, nkvsubbh
numberofrequestsACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) Number of authentication vector requests that were sent by the VLRs. The REQUEST contains the SYNCHRONISATION REQUEST.obsolete.obsoletenkmtbh, nkvsubbh
numberofsyncreqACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) The number of synchronisation request which can be sent when the mobile rejects the authentication because the sequence number is out of range.obsolete.obsoletenkmtbh, nkvsubbh
numberoftripletsINTENSITYINTEGER(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) Number of transferred authentication triplets. obsolete.obsoletenkmtbh, nkvsubbh
numberofunknownsubscINTENSITYINTEGER(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) Number of subscribers whose data cannot be found in the AUC of the HLR.obsolete.obsoletenkmtbh, nkvsubbh
nweishlrifvalueis_1ACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is HLR, which sent the authentication vector. In ASCII report appears HLR in NWE column.obsolete.obsoletenkmtbh, nkvsubbh
nweisplmnifvalueis_1ACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is PLMN, which sent the authentication vector. In this case the HLR address of the subscriber is unknown and the VLR calculates the HLR address from IMSI. In ASCII report appears PLMN in NWE column.obsolete.obsoletenkmtbh, nkvsubbh
nweisvlrifvalueis_1ACCUMULATIONINT8(Obsolete in M13.5, ACVSPV block now supported under Signalling_Point object) The allowed value for this counter is 1. If counter is sent in XML report with respective value it means that the network element is VLR, which sent the authentication vector. In ASCII report appears VLR in NWE column and the vectors came from the previous VLR after location update.obsolete.obsoletenkmtbh, nkvsubbh


VLR.Nokia.GSM.Subscribers

This section describes the counters of M80

KPITypeData TypeDescriptionDerivationAdditional Summaries
datamissing_in_subscvalues_hlrINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, that is, only a subset of the data could be collected. It means that the printed subscriber numbers per HLR are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)VLRNMSC.M339B2C1nkmtbh, nkvsubbh
datamissing_in_subscvalues_plmnINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, that is, only a subset of the data could be collected. It means that the printed subscriber numbers per PLMN are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)VLRNMSC.M340B2C1nkmtbh, nkvsubbh
datamissinginlaINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, i.e. only a subset of the data could be collected. It means that the printed LAC values are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)VLRNMSC.M80B2C1nkmtbh, nkvsubbh
datamissinginpagingperlaINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, that is, only a subset of the data could be collected. It means that the printed counters per LAC are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)VLRNMSC.M353B2C1nkmtbh, nkvsubbh
tot_ave_subscINTENSITYINTEGERTotal average number of subscribers in all location areasVLRNMSC.M80B2C6nkmtbh, nkvsubbh
tot_curr_subscINTENSITYINTEGERTotal current number of subscribers in all location areasVLRNMSC.M80B2C5nkmtbh, nkvsubbh


VLR.Nokia.GSM.TM_Subscribers

This section describes the counters of M78

KPITypeData TypeDescriptionDerivationAdditional Summaries
datamissinginlaINTENSITYINTEGERThis line is printed if data transfer from one or several VLRUs failed during one or more inquiries, i.e. only a subset of the data could be collected. It means that the printed LAC values are not reliable. (The problem can be overloaded VLRUs, a VLRU start-up.)VLRMSC.M78B3C1nkmtbh, nkvsubbh
totaltelemetricsubcat1INTENSITYINTEGERNumber of telemeteric subscribers category 1 in all location area at the reporting time. The maximum number of location areas in a report is 40. The telemeteric subscribers category 1, 2, and 3 will be presented only in case when the feature is active.VLRMSC.M78B2C1nkmtbh, nkvsubbh
totaltelemetricsubcat2INTENSITYINTEGERNumber of telemeteric subscribers category 2 in all location area at the reporting time. The maximum number of location areas in a report is 40. The telemeteric subscribers category 1, 2, and 3 will be presented only in case when the feature is active.VLRMSC.M78B2C2nkmtbh, nkvsubbh
totaltelemetricsubcat3INTENSITYINTEGERNumber of telemeteric subscriber s category 3 in all location area at the reporting time. The maximum number of location areas in a report is 40. The telemeteric subscribers category 1, 2, and 3 will be presented only in case when the feature is active.VLRMSC.M78B2C3nkmtbh, nkvsubbh


VLR.Nokia.GSM.TMSI_allocation

Temporary mobile subscriber identity allocation data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_tmsiallocationfailPERCENTAGEFLOATPercentage unsuccessful TMSI allocationpercentfail({tmsiallocationfail}, {tmsiallocationattempt})nkmtbh, nkvsubbh
%_tmsiallocationsuccPERCENTAGEFLOATPercentage successful TMSI allocationpercentok({tmsiallocationsucc}, {tmsiallocationattempt})nkmtbh, nkvsubbh
tmsiallocationattemptACCUMULATIONINT8TMSI allocation initiated by the VLR application. This counter is updated both for normal and telemeteric subscribers.VLR1MSC.M82B5C7nkmtbh, nkvsubbh
tmsiallocationfailACCUMULATIONINT8The TMSI allocation did not succeed, because the VLR could not allocate a new TMSI. This counter is updated both for normal and telemeteric subscribers.VLR1MSC.M82B5C9nkmtbh, nkvsubbh
tmsiallocationsuccACCUMULATIONINT8TMSI allocation is successfully performed and confirmed by the MS. This counter is updated both for normal and telemeteric subscribers.VLR1MSC.M82B5C8nkmtbh, nkvsubbh


VLR.Nokia.GSM.ULMC

ULMC data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
ulmc_data_missingACCUMULATIONINT8It shows that load control measurement data is missing from some or all units. If the data is missing from all units then the load management counters would not be printed afterwards at all. The possible value is 1 or this field does not appear in the report.VLR1MSC.M82B22C1nkmtbh, nkvsubbh
ulmc_inter_vlrlu_attemptsACCUMULATIONINT8All inter VLR location update attempts during measurement period. The trigger point for updating this counter is the point when the VLR receives the LOCATION UPDATING REQUEST message from a subscriber that is not currently registered in it.VLR1MSC.M82B22C12nkmtbh, nkvsubbh
ulmc_inter_vlrlu_rejectionsACCUMULATIONINT8All inter VLR location update rejections during measurement period made by traffic control. The trigger point for updating this counter is the point when VLR updates counter INTER-VLR LOCATION UPDATE ATTEMPTS and decides to reject the transaction becauseVLR1MSC.M82B22C13nkmtbh, nkvsubbh
ulmc_intra_vlrlu_attemptsACCUMULATIONINT8All intra VLR location update attempts during measurement period. The trigger point for updating this counter is the point when the VLR receives the LOCATION UPDATING REQUEST message from a subscriber that is already registered in it.VLR1MSC.M82B22C10nkmtbh, nkvsubbh
ulmc_intra_vlrlu_rejectionsACCUMULATIONINT8All intra VLR location update rejections during measurement period made by traffic control. The trigger point for updating this counter is the point when VLR updates counter INTRA-VLR LOCATION UPDATE ATTEMPTS and decides to reject the transaction becauseVLR1MSC.M82B22C11nkmtbh, nkvsubbh
ulmc_mo_call_attemptsACCUMULATIONINT8All mobile originating call transaction attempts during measurement period. The trigger point for updating this counter is the point when the VLR receives the access request message for mobile originated call.VLR1MSC.M82B22C2nkmtbh, nkvsubbh
ulmc_mo_call_rejectionsACCUMULATIONINT8All mobile originating call transaction rejections during measurement period made by traffic control. The trigger point for updating this counter is the point when VLR updates counter MOBILE ORIGINATING CALL ATTEMPTS and decides to reject the transactionVLR1MSC.M82B22C3nkmtbh, nkvsubbh
ulmc_mo_sms_attemptsACCUMULATIONINT8All mobile originating SMS attempts during measurement period. The trigger point for updating this counter is the point when the VLR receives the access request message for mobile originated short message.VLR1MSC.M82B22C6nkmtbh, nkvsubbh
ulmc_mo_sms_rejectionsACCUMULATIONINT8All mobile originating SMS rejections during measurement period made by traffic control. The trigger point for updating this counter is the point when VLR updates counter MOBILE ORIGINATING SMS ATTEMPTS and decides to reject the transaction because of theVLR1MSC.M82B22C7nkmtbh, nkvsubbh
ulmc_mt_call_attemptsACCUMULATIONINT8All mobile terminating call transaction attempts during measurement period. The trigger point for updating this counter is the point when the VMSC asks for subscribers basic service from VLR after receiving the IAM from the GMSC.VLR1MSC.M82B22C4nkmtbh, nkvsubbh
ulmc_mt_call_rejectionsACCUMULATIONINT8All mobile terminating call transaction rejections during measurement period made by traffic control. The trigger point for updating this counter is the point when VLR updates counter MOBILE TERMINATING CALL ATTEMPTS and decides to reject the transactionVLR1MSC.M82B22C5nkmtbh, nkvsubbh
ulmc_mt_sms_attemptsACCUMULATIONINT8All mobile terminating SMS attempts during measurement period. The trigger point for updating this counter is the point when the VLR receives the request for subscriber information for forwarding a mobile terminated short message.VLR1MSC.M82B22C8nkmtbh, nkvsubbh
ulmc_mt_sms_rejectionsACCUMULATIONINT8All mobile terminating SMS rejections during measurement period made by traffic control. The trigger point for updating this counter is the point when VLR updates counter MOBILE TERMINATING SMS ATTEMPTS and decides to reject the transaction because of theVLR1MSC.M82B22C9nkmtbh, nkvsubbh


VLR.Nokia.GSM.UMA_location_updates

Unlicenced Mobile Access location update data.

KPITypeData TypeDescriptionDerivationAdditional Summaries
arriv_visitor_oth_p_uma_attACCUMULATIONINT8UMA location update attempts for all visiting subscribers arriving from another visiting PLMN. The location updates in this field are already included in the value of the INTER VLR, ROAMING SUBSCRIBERS field.VLR1MSC.M82B3C148nkmtbh, nkvsubbh
arriv_visitor_oth_p_uma_succACCUMULATIONINT8Successful UMA location updates for all visiting subscribers arriving from another visiting PLMN. The location updates in this field are already included in the value of the INTER VLR, ROAMING SUBSCRIBERS field. New roaming subscribers (who have just purchased their SIMs) are updated in this field. In the SUCCESSFUL field, only the normal subscribers are counted.VLR1MSC.M82B3C149nkmtbh, nkvsubbh
inter_vlr_hs_uma_attACCUMULATIONINT8UMA location update attempts between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR). New home subscribers (who have just purchased their SIMs) are updated in this field. This fieldVLR1MSC.M82B3C138nkmtbh, nkvsubbh
inter_vlr_hs_uma_succACCUMULATIONINT8UMA successful location updates between VLRs performed by home subscribers (both those coming from another PLMN and the ones inside the network changing the VLR). New home subscribers (who have just purchased SIM) are updated in this field. This field isVLR1MSC.M82B3C139nkmtbh, nkvsubbh
inter_vlr_rs_uma_attACCUMULATIONINT8UMA location update attempts performed by visiting subscribers arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM. In the ATTEMPT field, both the normal and telemeterVLR1MSC.M82B3C144nkmtbh, nkvsubbh
inter_vlr_rs_uma_succACCUMULATIONINT8Successful UMA location updates performed by visiting normal subscribers arriving from other PLMN or changing the VLR within the same PLMN. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field, only the normalVLR1MSC.M82B3C145nkmtbh, nkvsubbh
intra_vlr_inter_p_hs_uma_attACCUMULATIONINT8UMA location update attempts between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs. The trigger point for updating this counter is the point when the VMSC receives the LOVLR1MSC.M82B3C136nkmtbh, nkvsubbh
intra_vlr_inter_p_hs_uma_succACCUMULATIONINT8Successful UMA location updates between location areas made by home normal subscribers inside the VLR but the original and target location areas belong to different PLMNs. The trigger point for updating this counter is the point when the VMSC sends the LOVLR1MSC.M82B3C137nkmtbh, nkvsubbh
intra_vlr_inter_p_rs_uma_attACCUMULATIONINT8UMA location update attempts performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs. The trigger point for updating this counter is the point when the VMSC receives the LOCATION UPDATING REQUEST message from UMA network.VLR1MSC.M82B3C142nkmtbh, nkvsubbh
intra_vlr_inter_p_rs_uma_succACCUMULATIONINT8Successful UMA location updates performed by visiting normal subscribers inside the VLR but the original and target location areas belong to different PLMNs. The trigger point for updating this counter is the point when the VMSC sends the LOCATION UPDATING ACCEPT message to UMA network.VLR1MSC.M82B3C143nkmtbh, nkvsubbh
intra_vlr_intra_p_hs_uma_attACCUMULATIONINT8UMA location update attempts between location areas made by home normal subscribers inside the VLR and within the same PLMN. The trigger point for updating this counter is the point when the VMSC receives the LOCATION UPDATING REQUEST message from UMA network.VLR1MSC.M82B3C134nkmtbh, nkvsubbh
intra_vlr_intra_p_hs_uma_succACCUMULATIONINT8Successful UMA location updates between location areas made by home normal subscribers inside the VLR and within the same PLMN. The trigger point for updating this counter is the point when the VMSC sends the LOCATION UPDATING ACCEPT message to UMA networkVLR1MSC.M82B3C135nkmtbh, nkvsubbh
intra_vlr_intra_p_rs_uma_attACCUMULATIONINT8UMA location update attempts performed by visiting normal subscribers inside the VLR and within the same PLMN. The trigger point for updating this counter is the point when the VMSC receives the LOCATION UPDATING REQUEST message from UMA network.VLR1MSC.M82B3C140nkmtbh, nkvsubbh
intra_vlr_intra_p_rs_uma_succACCUMULATIONINT8Successful UMA location updates performed by visiting normal subscribers inside the VLR and within the same PLMN. The trigger point for updating this counter is the point when the VMSC sends the LOCATION UPDATING ACCEPT message to UMA network.VLR1MSC.M82B3C141nkmtbh, nkvsubbh
lu_request_uma_attemptACCUMULATIONINT8It shows the total number of the requested UMA location update attempts from A interface or A+ interface from UMA network. The trigger point for updating this counter is the point when VMSC receives the LOCATION UPDATING REQUEST message from UMA network.VLR1MSC.M82B7C5nkmtbh, nkvsubbh
periodic_loc_reg_uma_attACCUMULATIONINT8UMA periodic location update attempts for all normal subscribers. The trigger point for updating this counter is the point when the VMSC receives the LOCATION UPDATING REQUEST message from UMA network.VLR1MSC.M82B3C146nkmtbh, nkvsubbh
periodic_loc_reg_uma_succACCUMULATIONINT8Successful UMA periodic location updates for all normal subscribers. The trigger point for updating this counter is the point when the VMSC sends the LOCATION UPDATING ACCEPT message to UMA network.VLR1MSC.M82B3C147nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_Alternate_Paging

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows alternate paging related measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
alter_paging_through_sgsn_attemptsACCUMULATIONINT8This counter contains the number of successful alternate pagings through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK.VLR1MSC.M82B4C11nkmtbh, nkvsubbh
alter_paging_through_sgsn_atttm1ACCUMULATIONINT8This counter contains the number of successful alternate pagings through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK. telemeteric subscriber category 1.VLR1MSC.M82B9C11nkmtbh, nkvsubbh
alter_paging_through_sgsn_atttm2ACCUMULATIONINT8This counter contains the number of successful alternate pagings through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK. telemeteric subscriber category 2.VLR1MSC.M82B12C11nkmtbh, nkvsubbh
alter_paging_through_sgsn_atttm3ACCUMULATIONINT8This counter contains the number of successful alternate pagings through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK. telemeteric subscriber category 3.VLR1MSC.M82B15C11nkmtbh, nkvsubbh
alter_paging_through_sgsn_succACCUMULATIONINT8This counter is optional, it contains the number of alternate paging attempts through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation.VLR1MSC.M82B4C10nkmtbh, nkvsubbh
alter_paging_through_sgsn_succtm1ACCUMULATIONINT8This counter contains the number of alternate paging attempts through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 1.VLR1MSC.M82B9C10nkmtbh, nkvsubbh
alter_paging_through_sgsn_succtm2ACCUMULATIONINT8This counter contains the number of alternate paging attempts through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 2.VLR1MSC.M82B12C10nkmtbh, nkvsubbh
alter_paging_through_sgsn_succtm3ACCUMULATIONINT8This counter contains the number of alternate paging attempts through A and Iu interface when the paging via Gs interface was unsuccessful. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 3.VLR1MSC.M82B15C10nkmtbh, nkvsubbh
paging_for_voice_attemptsACCUMULATIONINT8Number of paging requests without repagings that were sent on the A interface for mobile terminated voice calls.VLR1MSC.M82B4C12nkmtbh, nkvsubbh
paging_for_voice_succACCUMULATIONINT8Number of paging response messages received on the A interface for mobile terminated voice calls.VLR1MSC.M82B4C13nkmtbh, nkvsubbh
paging_on_aif_attemptsACCUMULATIONINT8The number of paging requests without repagings, which were actually sent out on the A-interface.VLR1MSC.M82B4C14nkmtbh, nkvsubbh
paging_on_aif_succACCUMULATIONINT8The number of paging response messages that were actually received on the A-interfaceVLR1MSC.M82B4C15nkmtbh, nkvsubbh
prevented_paging_vlrACCUMULATIONINT8The number of pagings failed because of paging prevention.VLR1MSC.M82B23C1nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_Departing_Subscribers

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows the departing subscriber information

KPITypeData TypeDescriptionDerivationAdditional Summaries
departingvisitorsattemptACCUMULATIONINT8Shows number of the normal subscribers (both home subscribers and visitors) departing from the VLR. The field is updated when a cancel location is received from the HLRVLR1MSC.M82B3C13nkmtbh, nkvsubbh
departingvisitorsattempttm1ACCUMULATIONINT8Obsolete in M13 - Shows number of the telemeteric subscribers category 1 (both home subscribers and visitors) departing from the VLR. The field is updated when a cancel location is received from the HLR.VLR1MSC.M82B8C13nkmtbh, nkvsubbh
departingvisitorsattempttm2ACCUMULATIONINT8Shows number of the telemeteric subscribers category 2 (both home subscribers and visitors) departing from the VLR. The field is updated when a cancel location is received from the HLR.VLR1MSC.M82B11C13nkmtbh, nkvsubbh
departingvisitorsattempttm3ACCUMULATIONINT8Shows number of the telemeteric subscribers category 3 (both home subscribers and visitors) departing from the VLR. The field is updated when a cancel location is received from the HLR.VLR1MSC.M82B14C13nkmtbh, nkvsubbh
succ_dep_visitsACCUMULATIONINT8Obsolete in M13 - Shows number of the normal subscribers (both home subscribers and visitors) departing from the VLR.VLR1MSC.M82B3C30nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_GPRS_GSM_UMTS

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows events that happened when the mobile is GPRS and GSM/UMTS attached

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_gprs_initiated_lusuccPERCENTAGEFLOATPercentage successful events when the mobile is GPRS and GSM/UMTS attached and MS makes a successful location update.percentok({gprs_initiated_lusucc}, {gprs_initiated_luattempt})nkmtbh, nkvsubbh
gprs_initiated_luattemptACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and MS makes a location update attempt. These events are also counted to the attempt LU countersVLR1MSC.M82B6C1nkmtbh, nkvsubbh
gprs_initiated_luattempttm1ACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and the MS makes a location update attempt. These events are also counted to the attempt LU counters. The trigger point for updating this counter is the point when VMSC receives the LOCATION UPDATING REQUEST message. telemeteric subscriber category 1.VLR1MSC.M82B6C3nkmtbh, nkvsubbh
gprs_initiated_luattempttm2ACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and the MS makes a location update attempt. These events are also counted to the attempt LU counters. The trigger point for updating this counter is the point when VMSC receives the LOCATION UPDATING REQUEST message. telemeteric subscriber category 2.VLR1MSC.M82B6C5nkmtbh, nkvsubbh
gprs_initiated_luattempttm3ACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and the MS makes a location update attempt. These events are also counted to the attempt LU counters. The trigger point for updating this counter is the point when VMSC receives the LOCATION UPDATING REQUEST message. telemeteric subscriber category 3.VLR1MSC.M82B6C7nkmtbh, nkvsubbh
gprs_initiated_lusuccACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and MS makes a successful location update. These events are also counted to the successful LU counters.VLR1MSC.M82B6C2nkmtbh, nkvsubbh
gprs_initiated_lusucctm1ACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and the MS makes a successful location update. These events are also counted to the successful LU counters. The trigger point for updating this counter is the point when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 1.VLR1MSC.M82B6C4nkmtbh, nkvsubbh
gprs_initiated_lusucctm2ACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and the MS makes a successful location update. These events are also counted to the successful LU counters. The trigger point for updating this counter is the point when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 2.VLR1MSC.M82B6C6nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_IMSI

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows IMSI related events

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_imsiattachgsmsuccPERCENTAGEFLOATPercentage successful GSM IMSI attachments.percentok({imsiattachgsmsucc}, {imsiattachgsmattempt})nkmtbh, nkvsubbh
attempt_imsi_attACCUMULATIONINT8Obsolete in M13 - The number of IMSI attach attempts.VLR1MSC.M82B5C1nkmtbh, nkvsubbh
imsi_attach_uma_attemptACCUMULATIONINT8Number of UMA IMSI attachments. This operation is only performed when the subscriber switches the mobile station on in the same location area where it was switched off. The ATTEMPT field includes both the normal and telemeteric subscribers IMSI attachmentVLR1MSC.M82B5C110nkmtbh, nkvsubbh
imsi_attach_uma_succACCUMULATIONINT8Number of UMA IMSI attachments. This operation is only performed when the subscriber switches the mobile station on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments.VLR1MSC.M82B5C111nkmtbh, nkvsubbh
imsi_detach_uma_attemptACCUMULATIONINT8Number of UMA IMSI detachments. This operation is performed when the subscriber switches the mobile station off. The trigger point for updating this counter is when the VMSC receives the IMSI DETACH INDICATION message.VLR1MSC.M82B5C112nkmtbh, nkvsubbh
imsi_detachACCUMULATIONINT8Obsolete in M13 - The number of IMSI detaches.VLR1MSC.M82B5C5nkmtbh, nkvsubbh
imsiattachgsmattemptACCUMULATIONINT8Number of GSM IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The ATTEMPT field includes both the normal and telemeteric subscribers IMSI attachments.VLR1MSC.M82B5C101nkmtbh, nkvsubbh
imsiattachgsmsuccACCUMULATIONINT8Number of GSM IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments.VLR1MSC.M82B5C103nkmtbh, nkvsubbh
imsiattachgsmsucctm1ACCUMULATIONINT8Number of GSM IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments. telemeteric subscriber category 1.VLR1MSC.M82B10C103nkmtbh, nkvsubbh
imsiattachgsmsucctm2ACCUMULATIONINT8Number of GSM IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments. telemeteric subscriber category 2.VLR1MSC.M82B13C103nkmtbh, nkvsubbh
imsiattachgsmsucctm3ACCUMULATIONINT8Number of GSM IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments. telemeteric subscriber category 3VLR1MSC.M82B16C103nkmtbh, nkvsubbh
imsidetachgsmattemptACCUMULATIONINT8Number of GSM IMSI detachments. This operation is performed when the subscriber switches the mobile phone off.VLR1MSC.M82B5C105nkmtbh, nkvsubbh
imsidetachgsmattempttm1ACCUMULATIONINT8GSM attempts of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters. telemeteric subscriber category 1.VLR1MSC.M82B10C105nkmtbh, nkvsubbh
imsidetachgsmattempttm2ACCUMULATIONINT8GSM attempts of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters. telemeteric subscriber category 2.VLR1MSC.M82B13C105nkmtbh, nkvsubbh
imsidetachgsmattempttm3ACCUMULATIONINT8GSM attempts of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters. telemeteric subscriber category 3.VLR1MSC.M82B16C105nkmtbh, nkvsubbh
succ_imsi_attACCUMULATIONINT8Obsolete in M13 - The number of successful IMSI attaches.VLR1MSC.M82B5C3nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_Location_Updates

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows location update related events

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_successful_lu_gsmPERCENTAGEFLOATPercentage successful location updates: GSMpercentok({total_lu_successes_gsm}, {total_lu_attempts_gsm})nkmtbh, nkvsubbh
%_successful_lu_umtsPERCENTAGEFLOATPercentage successful location updates: UMTSpercentok({total_lu_successes_umts}, {total_lu_attempts_umts})nkmtbh, nkvsubbh
%_successful_luPERCENTAGEFLOATPercentage successful location updates: GSM + UMTSpercentok({total_lu_successes}, {total_lu_attempts})nkmtbh, nkvsubbh
activearrivingscACCUMULATIONINT8The number of inter-VLR Location Updates when the arriving subscriber was already in active state in the database. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C8nkmtbh, nkvsubbh
activetopassivescACCUMULATIONINT8The number of inter-VLR Location Updates when the arriving subscriber was already in active state in the database. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C9nkmtbh, nkvsubbh
arrivvisitorothplmngsmattemptACCUMULATIONINT8GSM location update attempts for all visiting subscribers arriving from another visiting PLMN. The location updates in this field are already included in the value of the field INTER VLR, ROAMING SUBSCRIBERS. New roaming subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the ATTEMPT field both the normal and telemeteric subscribers are counted.VLR1MSC.M82B3C126nkmtbh, nkvsubbh
arrivvisitorothplmngsmsuccACCUMULATIONINT8GSM successful Location updates for all visiting subscribers arriving from another visiting PLMN. The location updates in this field are already included in the value of the field INTER VLR, ROAMING SUBSCRIBERS. New roaming subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field only the normal subscribers are counted.VLR1MSC.M82B3C127nkmtbh, nkvsubbh
arrivvisitorothplmngsmsucctm1ACCUMULATIONINT8GSM successful location updates for all visiting telemeteric subscribers category 1 arriving from another visiting PLMN.VLR1MSC.M82B8C127nkmtbh, nkvsubbh
arrivvisitorothplmngsmsucctm2ACCUMULATIONINT8GSM successful location updates for all visiting telemeteric subscribers category 2 arriving from another visiting PLMN.VLR1MSC.M82B11C127nkmtbh, nkvsubbh
arrivvisitorothplmngsmsucctm3ACCUMULATIONINT8GSM successful location updates for all visiting telemeteric subscribers category 3 arriving from another visiting PLMN.VLR1MSC.M82B14C127nkmtbh, nkvsubbh
attempt_arr_subscACCUMULATIONINT8Obsolete in M13 - GSM location update attempts for all visiting subscribers arriving from another visiting PLMN.VLR1MSC.M82B3C26nkmtbh, nkvsubbh
attempt_home_i_vlr_e_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of intra VLR inter PLMN location update attempts for home subscribers.VLR1MSC.M82B3C5nkmtbh, nkvsubbh
attempt_home_i_vlr_i_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of intra VLR intra PLMN location update attempts for home subscribers.VLR1MSC.M82B3C1nkmtbh, nkvsubbh
attempt_home_inter_vlr_luACCUMULATIONINT8Obsolete in m13.5 - The number of inter-VLR location update attempts for home subscribers.VLR1MSC.M82B3C6nkmtbh, nkvsubbh
attempt_period_luACCUMULATIONINT8Obsolete in M13 - The number of periodic location update attempts.VLR1MSC.M82B3C22nkmtbh, nkvsubbh
attempt_roam_i_vlr_e_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of intra VLR inter PLMN location update attempts for roaming subscribers.VLR1MSC.M82B3C14nkmtbh, nkvsubbh
attempt_roam_i_vlr_i_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of intra VLR intra PLMN location update attempts for roaming subscribers.VLR1MSC.M82B3C10nkmtbh, nkvsubbh
attempt_roam_inter_vlr_luACCUMULATIONINT8Obsolete in m13.5 - The number of inter-VLR location update attempts for roaming subscribers.VLR1MSC.M82B3C18nkmtbh, nkvsubbh
lu_update_reqACCUMULATIONINT8Obsolete in m13.5 - Location update requests. VLR1MSC.M82B7C1nkmtbh, nkvsubbh
luattemptnationalroamsubsACCUMULATIONINT8This counter is updated when a national roaming subscriber attempts to change location areas under the same VLR (normally during an intra-VLR LU). There is no differentiation between normal and telemeteric subscribers and between GSM and UMTS location updates. This counter is optional. It appears in the reports only if the national roaming feature is ON. Note: This counter includes all requests independently of their result and indicates whether the subscriber data update was finally skipped or not.VLR1MSC.M82B6C9nkmtbh, nkvsubbh
lurejectduedatabaseclACCUMULATIONINT8The number of rejected Location Updates because of the VLR DB is full. This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C4nkmtbh, nkvsubbh
lurejectduedatabasescACCUMULATIONINT8The number of rejected Location Updates because of the VLR DB is full. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C6nkmtbh, nkvsubbh
lurejectednationalroamsubsACCUMULATIONINT8This counter is updated when a national roaming subscriber tries to change location areas under the same VLR (normally during an intra-VLR LU) but the LU is rejected with the Roaming Not Allowed cause code. There is no differentiation between normal and telemeteric subscribers and between GSM and UMTS location updates. This counter is optional. It appears in the reports only if the national roaming feature is ON.VLR1MSC.M82B6C10nkmtbh, nkvsubbh
lurequestgsmattemptACCUMULATIONINT8Shows the total number of the requested GSM location update attempts from A interfaceVLR1MSC.M82B7C3nkmtbh, nkvsubbh
lusuccessnationalroamsubsACCUMULATIONINT8This counter is updated when a national roaming subscriber successfully changes location areas under the same VLR (normally during an intra-VLR LU) and the VLR triggers an extra UpdateLocation procedure towards the HLR. There is no differentiation between normal and telemeteric subscribers and between GSM and UMTS location updates. The successful attempts are responded to immediately without updating the subscriber data to the VLR. This counter is optional. It appears in the reports only if the national roaming feature is ON.VLR1MSC.M82B6C11nkmtbh, nkvsubbh
luwithoutisdscACCUMULATIONINT8The number of inter-VLR Location Update procedures without Insert Subscriber Data procedure. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C7nkmtbh, nkvsubbh
periodiclocreggsmattemptACCUMULATIONINT8GSM periodic location update attempts for all normal subscribers.VLR1MSC.M82B3C122nkmtbh, nkvsubbh
periodiclocreggsmattempttm1ACCUMULATIONINT8GSM periodic location update attempts for all telemeteric subscribers category 1VLR1MSC.M82B8C122nkmtbh, nkvsubbh
periodiclocreggsmattempttm2ACCUMULATIONINT8GSM periodic location update attempts for all telemeteric subscribers category 2VLR1MSC.M82B11C122nkmtbh, nkvsubbh
periodiclocreggsmattempttm3ACCUMULATIONINT8GSM periodic location update attempts for all telemeteric subscribers category 3VLR1MSC.M82B14C122nkmtbh, nkvsubbh
periodiclocreggsmsuccACCUMULATIONINT8GSM successful periodic location update attempts for all normal subscribers.VLR1MSC.M82B3C123nkmtbh, nkvsubbh
periodiclocreggsmsucctm1ACCUMULATIONINT8GSM successful periodic location updates for all telemeteric subscribers category 1VLR1MSC.M82B8C123nkmtbh, nkvsubbh
periodiclocreggsmsucctm2ACCUMULATIONINT8GSM successful periodic location updates for all telemeteric subscribers category 2VLR1MSC.M82B11C123nkmtbh, nkvsubbh
periodiclocreggsmsucctm3ACCUMULATIONINT8GSM successful periodic location updates for all telemeteric subscribers category 3VLR1MSC.M82B14C123nkmtbh, nkvsubbh
SIP_PERIODIC_LU_ATTEMPTACCUMULATIONINT8The periodic location update attempts during a SIP reregistration procedure. It is printed only if the NVS feature is active.VLR1MSC.M82B6C12nkmtbh, nkvsubbh
SIP_PERIODIC_LU_SUCCACCUMULATIONINT8The successful periodic location update, that is, MAP UpdateLocationAck received, during a reregistration. It is printed only if the NVS feature is active.VLR1MSC.M82B6C13nkmtbh, nkvsubbh
succ_arr_visitsACCUMULATIONINT8Obsolete in m13.5 - GSM successful Location updates for all visiting subscribers arriving from another visiting PLMN.VLR1MSC.M82B3C27nkmtbh, nkvsubbh
succ_home_i_vlr_e_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of successful intra VLR inter PLMN location updates for home subscribers.VLR1MSC.M82B3C31nkmtbh, nkvsubbh
succ_home_i_vlr_i_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of successful intra VLR intra PLMN location updates for home subscribers.VLR1MSC.M82B3C2nkmtbh, nkvsubbh
succ_home_inter_vlr_luACCUMULATIONINT8Obsolete in m13.5 - The number of successful inter-VLR location updates for home subscribers.VLR1MSC.M82B3C7nkmtbh, nkvsubbh
succ_period_luACCUMULATIONINT8Obsolete in M13 - The number of successful periodic location updates.VLR1MSC.M82B3C23nkmtbh, nkvsubbh
succ_roam_i_vlr_e_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of successful intra VLR inter PLMN location updates for roaming subscribers.VLR1MSC.M82B3C15nkmtbh, nkvsubbh
succ_roam_i_vlr_i_plmn_tms3ACCUMULATIONINT8Obsolete in m13.5 - The number of successful intra VLR intra PLMN location updates for roaming subscribers-TmS3. VLR1MSC.M82B14C11nkmtbh, nkvsubbh
succ_roam_i_vlr_i_plmnACCUMULATIONINT8Obsolete in m13.5 - The number of successful intra VLR intra PLMN location updates for roaming subscribers.VLR1MSC.M82B3C11nkmtbh, nkvsubbh
succ_roam_inter_vlr_luACCUMULATIONINT8Obsolete in m13.5 - The number of successful inter-VLR location updates for roaming subscribers.VLR1MSC.M82B3C19nkmtbh, nkvsubbh
total_lu_attempts_gsmACCUMULATIONINT8Total number of location update attempts: GSM{VLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnhsgsmattempt} + {VLR.Nokia.GSM.Inter_VLR_GSM.intervlrrsgsmattempt} + {VLR.Nokia.GSM.Inter_VLR_GSM.intervlrhsgsmattempt} + {VLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnrsgsmattempt} + {VLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnrsgsmattempt} + {VLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnhsgsmattempt} + {periodiclocreggsmattempt} + {VLR.Nokia.GSM.VLR_IMSI.imsiattachgsmattempt}nkmtbh, nkvsubbh
total_lu_attempts_umtsACCUMULATIONINT8Total number of location update attempts: UMTS{VLR.Nokia.GSM.Intra_VLR_UMTS.intravlrintraplmnhsumtsattempt} + {VLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_hs_umts_attempt} + {VLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_hs_umts_attempt} + {VLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_intra_plmn_rs_umts_attempt} + {VLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_rs_umts_attempt} + {VLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_rs_umts_attempt} + {VLR.Nokia.GSM.VLR_UMTS.period_ic_locreg_umts_attempt} + {VLR.Nokia.GSM.VLR_UMTS.imsi_attach_umts_attempt}nkmtbh, nkvsubbh
total_lu_attemptsACCUMULATIONINT8Total number of location update attempts: GSM + UMTS{total_lu_attempts_gsm} + {total_lu_attempts_umts}nkmtbh, nkvsubbh
total_lu_successes_gsmACCUMULATIONINT8Total number of successful location updates: GSM{VLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnhsgsmsucc} + {VLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnhsgsmsucc} + {VLR.Nokia.GSM.Inter_VLR_GSM.intervlrhsgsmsucc} + {VLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnrsgsmsucc} + {VLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnrsgsmsucc} + {periodiclocreggsmsucc} + {VLR.Nokia.GSM.VLR_IMSI.imsiattachgsmsucc}nkmtbh, nkvsubbh
total_lu_successes_umtsACCUMULATIONINT8Total number of successful location updates: UMTS{VLR.Nokia.GSM.Intra_VLR_UMTS.intravlrintraplmnhsumtssucc} + {VLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_hs_umts_succ} + {VLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_hs_umts_succ} + {VLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_intra_plmn_rs_umts_succ}+{VLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_rs_umts_succ} + {VLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_rs_umts_succ} + {VLR.Nokia.GSM.VLR_UMTS.period_ic_locreg_umts_succ} + {VLR.Nokia.GSM.VLR_UMTS.imsi_attach_umts_succ}nkmtbh, nkvsubbh
total_lu_successesACCUMULATIONINT8Total number of successful location updates: GSM + UMTS{total_lu_successes_gsm} + {total_lu_successes_umts}nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_Paging

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows paging related events

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_successful_pagingsPERCENTAGEFLOATPercentage successful pages: search + CS + PS + alt CSpercentok({total_paging_successes}, {total_paging_attempts})nkmtbh, nkvsubbh
attempt_pageACCUMULATIONINT8The number of paging attempts. VLR1MSC.M82B4C7nkmtbh, nkvsubbh
ms_searchatt_failACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is failed. (available for SEARCHING only)VLR1MSC.M82B4C4nkmtbh, nkvsubbh
ms_searchatt_failtm1ACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is failed. (available for SEARCHING only) telemeteric subscriber category 1.VLR1MSC.M82B9C6nkmtbh, nkvsubbh
ms_searchatt_failtm2ACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is failed. (available for SEARCHING only) telemeteric subscriber category 2.VLR1MSC.M82B12C6nkmtbh, nkvsubbh
ms_searchatt_failtm3ACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is failed. (available for SEARCHING only) telemeteric subscriber category 3.VLR1MSC.M82B15C6nkmtbh, nkvsubbh
ms_searchatt_succACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is successful. (available for SEARCHING only)VLR1MSC.M82B4C2nkmtbh, nkvsubbh
ms_searchatt_succtm1ACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is successful. (available for SEARCHING only) telemeteric subscriber category 1.VLR1MSC.M82B9C5nkmtbh, nkvsubbh
ms_searchatt_succtm2ACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is successful. (available for SEARCHING only) telemeteric subscriber category 2.VLR1MSC.M82B12C5nkmtbh, nkvsubbh
ms_searchatt_succtm3ACCUMULATIONINT8This counter shows the number of paging requests sent to A and Iu interface (from MSC) during the measurement period when the paging result is successful. (available for SEARCHING only) telemeteric subscriber category 3.VLR1MSC.M82B15C5nkmtbh, nkvsubbh
subscriberbusyACCUMULATIONINT8This counter shows the number of pagings (both CS and PS domain) and searchings when the subscriber is busy.VLR1MSC.M82B17C1nkmtbh, nkvsubbh
subscriberbusytm1ACCUMULATIONINT8This counter shows the number of pagings (both CS and PS domain) and searchings when the subscriber is busy. telemeteric subscriber category 1.VLR1MSC.M82B17C2nkmtbh, nkvsubbh
subscriberbusytm2ACCUMULATIONINT8This counter shows the number of pagings (both CS and PS domain) and searchings when the subscriber is busy. telemeteric subscriber category 2.VLR1MSC.M82B17C3nkmtbh, nkvsubbh
subscriberbusytm3ACCUMULATIONINT8This counter shows the number of pagings (both CS and PS domain) and searchings when the subscriber is busy. telemeteric subscriber category 3.VLR1MSC.M82B17C4nkmtbh, nkvsubbh
succ_pageACCUMULATIONINT8The number of successful paging attempts.VLR1MSC.M82B4C3nkmtbh, nkvsubbh
total_paging_attemptsACCUMULATIONINT8Paging attempts: search + CS + PS + alt CS{attempt_page} + {VLR.Nokia.GSM.VLR_TMS2.attempt_ms} + {VLR.Nokia.GSM.VLR_SGSN.attempt_sgsn} + {VLR.Nokia.GSM.VLR_Alternate_Paging.alter_paging_through_sgsn_succ}nkmtbh, nkvsubbh
total_paging_successesACCUMULATIONINT8Successful pages: search + CS + PS + alt CS{succ_page} + {VLR.Nokia.GSM.VLR_TMS2.succ_ms} + {VLR.Nokia.GSM.VLR_SGSN.succ_sgsn} + {VLR.Nokia.GSM.VLR_Alternate_Paging.alter_paging_through_sgsn_attempts}nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_Resources

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows resources

KPITypeData TypeDescriptionDerivationAdditional Summaries
used_sp_in_vlrdbINTENSITYFLOATThe used space in VLR database.VLR1MSC.M82B2C1nkmtbh, nkvsubbh
vlru_in_mscACCUMULATIONINT8The number of VLRU units in the MSC.VLR1MSC.M82B2C2nkmtbh, nkvsubbh
vlru_sentACCUMULATIONINT8The number of VLRU units that have sent data.VLR1MSC.M82B2C3nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_Search

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows search related events

KPITypeData TypeDescriptionDerivationAdditional Summaries
mssearchattemptstm1ACCUMULATIONINT8Search attempts done through all A and Iu interface and Serving GPRS Support Node (SGSN). telemeteric subscriber category 1.VLR1MSC.M82B9C2nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_SGSN

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows SGSN related measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_gprs_init_imsi_attach_succPERCENTAGEFLOATPercentage successful events when the SGSN sends the IMSI attach.percentok({gprs_init_imsi_attach_succ}, {gprs_init_imsi_attach_attempt})nkmtbh, nkvsubbh
%_successful_sgsn_pagingPERCENTAGEFLOATPercentage successful SGSN pagings.percentok({succ_sgsn}, {attempt_sgsn})nkmtbh, nkvsubbh
attempt_sgsnACCUMULATIONINT8The number of SGSN paging attempts.VLR1MSC.M82B4C9nkmtbh, nkvsubbh
gprs_init_imsi_attach_attemptACCUMULATIONINT8Attempts of events when the SGSN sends the IMSI attach. These events are also counted to the general attach countersVLR1MSC.M82B18C1nkmtbh, nkvsubbh
gprs_init_imsi_attach_attempttm1ACCUMULATIONINT8Attempts of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when the VMSC receives the LOCATION UPDATING REQUEST message. telemeteric subscriber category 1.VLR1MSC.M82B18C4nkmtbh, nkvsubbh
gprs_init_imsi_attach_attempttm2ACCUMULATIONINT8Attempts of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when the VMSC receives the LOCATION UPDATING REQUEST message. telemeteric subscriber category 2.VLR1MSC.M82B18C7nkmtbh, nkvsubbh
gprs_init_imsi_attach_attempttm3ACCUMULATIONINT8Attempts of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when the VMSC receives the LOCATION UPDATING REQUEST message. telemeteric subscriber category 3.VLR1MSC.M82B18C10nkmtbh, nkvsubbh
gprs_init_imsi_attach_succACCUMULATIONINT8Successfulness of events when the SGSN sends the IMSI attach. These events are also counted to the general attach countersVLR1MSC.M82B18C2nkmtbh, nkvsubbh
gprs_init_imsi_attach_succtm1ACCUMULATIONINT8Successfulness of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 1.VLR1MSC.M82B18C5nkmtbh, nkvsubbh
gprs_init_imsi_attach_succtm2ACCUMULATIONINT8Successfulness of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 2.VLR1MSC.M82B18C8nkmtbh, nkvsubbh
gprs_init_imsi_attach_succtm3ACCUMULATIONINT8Obsolete in M13 - Successfulness of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 3.VLR1MSC.M82B18C201nkmtbh, nkvsubbh
gprs_init_imsi_detach_attemptACCUMULATIONINT8Successfulness of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters.VLR1MSC.M82B18C3nkmtbh, nkvsubbh
gprs_init_imsi_detach_attempttm1ACCUMULATIONINT8Successfulness of events when the SGSN initiates an explicit IMSI detach to the VLR. These events are also counted to the general detach counters. The trigger point for updating this counter is the VMSC receives the IMSI DETACH INDICATION message. telemeteric subscriber category 1.VLR1MSC.M82B18C6nkmtbh, nkvsubbh
gprs_init_imsi_detach_attempttm2ACCUMULATIONINT8Successfulness of events when the SGSN initiates an explicit IMSI detach to the VLR. These events are also counted to the general detach counters. The trigger point for updating this counter is the VMSC receives the IMSI DETACH INDICATION message. telemeteric subscriber category 2.VLR1MSC.M82B18C9nkmtbh, nkvsubbh
gprs_init_imsi_detach_attempttm3ACCUMULATIONINT8Obsolete in m13.5 - Successfulness of events when the SGSN initiates an explicit IMSI detach to the VLR. These events are also counted to the general detach counters. The trigger point for updating this counter is the VMSC receives the IMSI DETACH INDICATION message. telemeteric subscriber category 3.VLR1MSC.M82B18C202nkmtbh, nkvsubbh
gprs_initiated_lusucctm3ACCUMULATIONINT8This counter shows the number of events happened when the mobile is GPRS and GSM/UMTS attached and the MS makes a successful location update. These events are also counted to the successful LU counters. The trigger point for updating this counter is the point when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 3.VLR1MSC.M82B6C8nkmtbh, nkvsubbh
gprsinitimsiattachsucctm3ACCUMULATIONINT8Successfulness of events when the SGSN sends the IMSI attach. These events are also counted to the general attach counters. The trigger point for updating this counter is when VMSC sends the LOCATION UPDATING ACCEPT message. telemeteric subscriber category 3.VLR1MSC.M82B18C11nkmtbh, nkvsubbh
gprsinitimsidetachattempttm3ACCUMULATIONINT8Successfulness of events when the SGSN initiates an explicit IMSI detach to the VLR. These events are also counted to the general detach counters. The trigger point for updating this counter is the VMSC receives the IMSI DETACH INDICATION message. telemeteric subscriber category 3.VLR1MSC.M82B18C12nkmtbh, nkvsubbh
paging_through_sgsn_attemptstm1ACCUMULATIONINT8Paging attempts done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 1.VLR1MSC.M82B9C8nkmtbh, nkvsubbh
paging_through_sgsn_attemptstm2ACCUMULATIONINT8Paging attempts done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 2.VLR1MSC.M82B12C8nkmtbh, nkvsubbh
paging_through_sgsn_attemptstm3ACCUMULATIONINT8Paging attempts done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 3.VLR1MSC.M82B15C8nkmtbh, nkvsubbh
paging_through_sgsn_succtm1ACCUMULATIONINT8Successful pagings done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK. telemeteric subscriber category 1.VLR1MSC.M82B9C7nkmtbh, nkvsubbh
paging_through_sgsn_succtm2ACCUMULATIONINT8Successful pagings done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK. telemeteric subscriber category 2.VLR1MSC.M82B12C7nkmtbh, nkvsubbh
paging_through_sgsn_succtm3ACCUMULATIONINT8Successful pagings done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated when Result is OK. telemeteric subscriber category 3.VLR1MSC.M82B15C7nkmtbh, nkvsubbh
pagingthroughaifattemptstm1ACCUMULATIONINT8Paging attempts done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 1.VLR1MSC.M82B9C4nkmtbh, nkvsubbh
pagingthroughaifattemptstm2ACCUMULATIONINT8Paging attempts done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 2.VLR1MSC.M82B12C4nkmtbh, nkvsubbh
pagingthroughaifattemptstm3ACCUMULATIONINT8Paging attempts done through SGSN. The trigger point for updating this counter is when VLR receives Paging Result message from MSC. This counter is updated independently from the result of the paging operation. telemeteric subscriber category 3.VLR1MSC.M82B15C4nkmtbh, nkvsubbh
succ_sgsnACCUMULATIONINT8The number of successful SGSN pagings.VLR1MSC.M82B4C5nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_subscribers

VLR subscriber data (supercharge feature).

KPITypeData TypeDescriptionDerivationAdditional Summaries
activesubscrtargetscACCUMULATIONINT8This counter shows the target for the active subscribers. Equals to the Target DB fill ratio (configurable parameter) multiplied by the limit for the active subscribers. This counter is printed only with the supercharger featureVLR1MSC.M82B20C3nkmtbh, nkvsubbh
capacitydatamissingACCUMULATIONINT8Missing capacity data from vlr application. This counter is printed only with the supercharger/advanced database handling feature. The XML counter contains value 1 if there was missing data.VLR1MSC.M82B21C1nkmtbh, nkvsubbh
maximumsubscribersclINTENSITYINTEGERThe limit for the number of subscribers in the VLR (maximum number of subscribers). This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C3nkmtbh, nkvsubbh
nbrofdeletedsubsactivescACCUMULATIONINT8Number of active subscribers deleted from the VLR during the measurement period. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C14nkmtbh, nkvsubbh
nbrofdeletedsubsclINTENSITYINTEGERNumber of subscribers deleted from the VLR during the measurement period. This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C5nkmtbh, nkvsubbh
nbrofdeletedsubspassivescACCUMULATIONINT8Number of passive subscribers deleted from the VLR during the measurement period. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C15nkmtbh, nkvsubbh
numofactivesubscrscINTENSITYINTEGERNumber of active subscribers in the VLR DB at the report generation time. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C1nkmtbh, nkvsubbh
numofpassivesubscrscINTENSITYINTEGERNumber of passive subscribers in the VLR DB at the report generation time. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C2nkmtbh, nkvsubbh
numofsubscractualclINTENSITYINTEGERNumber of subscribers in the VLR DB at the report generation time. This counter is printed only with the advanced database cleaning feature.VLR1MSC.M82B19C1nkmtbh, nkvsubbh
passivesubscrtargetscACCUMULATIONINT8Shows the limit for the active subscribers. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C4nkmtbh, nkvsubbh
passivetoactivescACCUMULATIONINT8Number of state changes of subscribers from passive to active in the VLR DB during the measurement period. This counter is printed only with the supercharger feature.VLR1MSC.M82B20C10nkmtbh, nkvsubbh
subscrtargetclACCUMULATIONINT8The target number of subscribers in the VLR DB. Equals to Target DB fill ratio (configurable parameter) multiplied by the limit for the number of subscribers in the VLR (maximum number of subscribers). This counter is printed only with the advanced databaseVLR1MSC.M82B19C2nkmtbh, nkvsubbh
totalsubscriberlimitscACCUMULATIONINT8Limit of subscribers in the VLR DB (maximum number of active and passive subscribers all together) This counter is printed only with the supercharger feature.VLR1MSC.M82B20C5nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_TMS1

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows TMS1 measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
attempt_home_i_vlr_e_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 intra VLR inter PLMN location update attempts for home subscribers.VLR1MSC.M82B8C5nkmtbh, nkvsubbh
attempt_home_i_vlr_i_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 intra VLR intra PLMN location update attempts for home subscribers.VLR1MSC.M82B8C1nkmtbh, nkvsubbh
attempt_period_lu_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 periodic location update attempts.VLR1MSC.M82B8C22nkmtbh, nkvsubbh
attempt_roam_i_vlr_e_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 intra VLR inter PLMN location update attempts for roaming subscribers.VLR1MSC.M82B8C14nkmtbh, nkvsubbh
attempt_roam_i_vlr_i_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 intra VLR intra PLMN location update attempts for roaming subscribers.VLR1MSC.M82B8C10nkmtbh, nkvsubbh
dep_subsc_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 departing subscribers.VLR1MSC.M82B8C30nkmtbh, nkvsubbh
imsi_detach_tms1ACCUMULATIONINT8Obsolete in M13 - The number of TmS1 IMSI detaches.VLR1MSC.M82B10C5nkmtbh, nkvsubbh
succ_arr_subsc_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 arriving subscribers.VLR1MSC.M82B8C27nkmtbh, nkvsubbh
succ_home_i_vlr_e_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 intra VLR inter PLMN location updates for home subscribers.VLR1MSC.M82B8C31nkmtbh, nkvsubbh
succ_home_i_vlr_i_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 intra VLR intra PLMN location updates for home subscribers.VLR1MSC.M82B8C2nkmtbh, nkvsubbh
succ_home_inter_vlr_lu_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 inter-VLR location updates for home subscribers.VLR1MSC.M82B8C7nkmtbh, nkvsubbh
succ_imsi_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 IMSI attaches.VLR1MSC.M82B10C3nkmtbh, nkvsubbh
succ_ms_tms1ACCUMULATIONINT8The number of successful TmS1 MS search.VLR1MSC.M82B9C1nkmtbh, nkvsubbh
succ_page_tms1ACCUMULATIONINT8The number of successful TmS1 pagings. VLR1MSC.M82B9C3nkmtbh, nkvsubbh
succ_period_lu_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 periodic location updates.VLR1MSC.M82B8C23nkmtbh, nkvsubbh
succ_roam_i_vlr_e_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 intra VLR inter PLMN location updates for roaming subscribers.VLR1MSC.M82B8C15nkmtbh, nkvsubbh
succ_roam_i_vlr_i_plmn_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 intra VLR intra PLMN location updates for roaming subscribers.VLR1MSC.M82B8C11nkmtbh, nkvsubbh
succ_roam_inter_vlr_lu_tms1ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS1 inter-VLR location updates for roaming subscribers.VLR1MSC.M82B8C19nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_TMS2

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows TMS2 measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
attempt_home_i_vlr_e_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 intra VLR inter PLMN location update attempts for home subscribers.VLR1MSC.M82B11C5nkmtbh, nkvsubbh
attempt_home_i_vlr_i_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 intra VLR intra PLMN location update attempts for home subscribers.VLR1MSC.M82B11C1nkmtbh, nkvsubbh
attempt_msACCUMULATIONINT8The number of MS search attempts. VLR1MSC.M82B4C8nkmtbh, nkvsubbh
attempt_period_lu_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 periodic location update attempts.VLR1MSC.M82B11C22nkmtbh, nkvsubbh
attempt_roam_i_vlr_e_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 intra VLR inter PLMN location update attempts for roaming subscribers.VLR1MSC.M82B11C14nkmtbh, nkvsubbh
attempt_roam_i_vlr_i_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 intra VLR intra PLMN location update attempts for roaming subscribers.VLR1MSC.M82B11C10nkmtbh, nkvsubbh
dep_subsc_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 departing subscribers.VLR1MSC.M82B11C30nkmtbh, nkvsubbh
imsi_detach_tms2ACCUMULATIONINT8Obsolete in M13 - The number of TmS2 IMSI detaches.VLR1MSC.M82B13C5nkmtbh, nkvsubbh
mssearchattemptstm2ACCUMULATIONINT8Search attempts done through all A and Iu interface and Serving GPRS Support Node (SGSN). telemeteric subscriber category 2.VLR1MSC.M82B12C2nkmtbh, nkvsubbh
mssearchattemptstm3ACCUMULATIONINT8Search attempts done through all A and Iu interface and Serving GPRS Support Node (SGSN). telemeteric subscriber category 3.VLR1MSC.M82B15C2nkmtbh, nkvsubbh
succ_arr_subsc_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 arriving subscribers.VLR1MSC.M82B11C27nkmtbh, nkvsubbh
succ_home_i_vlr_e_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 intra VLR inter PLMN location updates for home subscribers.VLR1MSC.M82B11C31nkmtbh, nkvsubbh
succ_home_i_vlr_i_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 intra VLR intra PLMN location updates for home subscribers.VLR1MSC.M82B11C2nkmtbh, nkvsubbh
succ_home_inter_vlr_lu_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 inter-VLR location updates for home subscribers.VLR1MSC.M82B11C7nkmtbh, nkvsubbh
succ_imsi_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 IMSI attaches.VLR1MSC.M82B13C3nkmtbh, nkvsubbh
succ_ms_tms2ACCUMULATIONINT8The number of successful TmS2 MS search.VLR1MSC.M82B12C1nkmtbh, nkvsubbh
succ_msACCUMULATIONINT8The number of successful MS search.VLR1MSC.M82B4C1nkmtbh, nkvsubbh
succ_page_tms2ACCUMULATIONINT8The number of successful TmS2 pagings. VLR1MSC.M82B12C3nkmtbh, nkvsubbh
succ_period_lu_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 periodic location updates.VLR1MSC.M82B11C23nkmtbh, nkvsubbh
succ_roam_i_vlr_i_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - Number of successful TmS2 intra VLR intra PLMN location updates for roaming subscribers.VLR1MSC.M82B11C11nkmtbh, nkvsubbh
succ_roam_inter_vlr_lu_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS2 inter-VLR location updates for roaming subscribers.VLR1MSC.M82B11C19nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_TMS3

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows TMS3 measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
attempt_home_i_vlr_e_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 intra VLR inter PLMN location update attempts for home subscribers.VLR1MSC.M82B14C5nkmtbh, nkvsubbh
attempt_home_i_vlr_i_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 intra VLR intra PLMN location update attempts for home subscribers.VLR1MSC.M82B14C1nkmtbh, nkvsubbh
attempt_period_lu_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 periodic location update attempts.VLR1MSC.M82B14C22nkmtbh, nkvsubbh
attempt_roam_i_vlr_e_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 intra VLR inter PLMN location update attempts for roaming subscribers.VLR1MSC.M82B14C14nkmtbh, nkvsubbh
attempt_roam_i_vlr_i_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 intra VLR intra PLMN location update attempts for roaming subscribers.VLR1MSC.M82B14C10nkmtbh, nkvsubbh
dep_subsc_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 departing subscribers.VLR1MSC.M82B14C30nkmtbh, nkvsubbh
imsi_detach_tms3ACCUMULATIONINT8Obsolete in M13 - The number of TmS3 IMSI detaches.VLR1MSC.M82B16C5nkmtbh, nkvsubbh
succ_arr_subsc_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 arriving subscribers.VLR1MSC.M82B14C27nkmtbh, nkvsubbh
succ_home_i_vlr_e_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 intra VLR inter PLMN location updates for home subscribers.VLR1MSC.M82B14C31nkmtbh, nkvsubbh
succ_home_i_vlr_i_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 intra VLR intra PLMN location updates for home subscribers.VLR1MSC.M82B14C2nkmtbh, nkvsubbh
succ_home_inter_vlr_lu_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 inter-VLR location updates for home subscribers.VLR1MSC.M82B14C7nkmtbh, nkvsubbh
succ_imsi_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 IMSI attaches.VLR1MSC.M82B16C3nkmtbh, nkvsubbh
succ_ms_tms3ACCUMULATIONINT8The number of successful TmS3 MS search. VLR1MSC.M82B15C1nkmtbh, nkvsubbh
succ_page_tms3ACCUMULATIONINT8The number of successful TmS3 pagings. VLR1MSC.M82B15C3nkmtbh, nkvsubbh
succ_period_lu_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 periodic location updates.VLR1MSC.M82B14C23nkmtbh, nkvsubbh
succ_roam_i_vlr_e_plmn_tms2ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 intra VLR inter PLMN location updates for roaming subscribers.VLR1MSC.M82B11C15nkmtbh, nkvsubbh
succ_roam_i_vlr_e_plmn_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 intra VLR inter PLMN location updates for roaming subscriber.VLR1MSC.M82B14C15nkmtbh, nkvsubbh
succ_roam_inter_vlr_lu_tms3ACCUMULATIONINT8Obsolete in M13 - The number of successful TmS3 inter-VLR location updates for roaming subscribers.VLR1MSC.M82B14C19nkmtbh, nkvsubbh


VLR.Nokia.GSM.VLR_UMTS

The VLR measurement contains information on subscriber movements, call establishment and IMSI attach and detach. This part shows UMTS related measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
arriv_visitor_othplmn_umts_attemptACCUMULATIONINT8UMTS location update attempts for all visiting subscribers arriving from another visiting PLMN. The location updates in this field are already included in the value of the field INTER VLR, ROAMING SUBSCRIBERS. New roaming subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the ATTEMPT field both the normal and telemeteric subscribers are counted.VLR1MSC.M82B3C128nkmtbh, nkvsubbh
arriv_visitor_othplmn_umts_succtm1ACCUMULATIONINT8UMTS successful location updates for all visiting telemeteric subscribers category 1 arriving from another visiting PLMN.VLR1MSC.M82B8C129nkmtbh, nkvsubbh
arriv_visitor_othplmn_umts_succtm2ACCUMULATIONINT8UMTS successful location updates for all visiting telemeteric subscribers category 2 arriving from another visiting PLMN.VLR1MSC.M82B11C129nkmtbh, nkvsubbh
arriv_visitor_othplmn_umts_succtm3ACCUMULATIONINT8UMTS successful location updates for all visiting telemeteric subscribers category 3 arriving from another visiting PLMN.VLR1MSC.M82B14C129nkmtbh, nkvsubbh
arriv_visitor_othplmn_umts_succACCUMULATIONINT8UMTS successful Location updates for all visiting subscribers arriving from another visiting PLMN. The location updates in this field are already included in the value of the field INTER VLR, ROAMING SUBSCRIBERS. New roaming subscribers (just purchased SIM) are updated in this field. This field is also updated if there is no location information in the SIM. In the SUCCESSFUL field only the normal subscribers are counted.VLR1MSC.M82B3C129nkmtbh, nkvsubbh
IMSI_ATTACH_SIP_ATTEMPTACCUMULATIONINT8It is updated during an initial registration when the SPD makes an IMSI attach. It is printed only if the NVS feature is active.VLR1MSC.M82B5C107nkmtbh, nkvsubbh
IMSI_ATTACH_SIP_SUCCACCUMULATIONINT8It is updated when VLR sends IMSI_Attach_Ack in case of initial registration. It is printed only if the NVS feature is active.VLR1MSC.M82B5C108nkmtbh, nkvsubbh
imsi_attach_umts_attemptACCUMULATIONINT8Number of UMTS IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The ATTEMPT field includes both the normal and telemeteric subscribers IMSI attachments.VLR1MSC.M82B5C102nkmtbh, nkvsubbh
imsi_attach_umts_succACCUMULATIONINT8Number of UMTS IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments.VLR1MSC.M82B5C104nkmtbh, nkvsubbh
imsi_attach_umts_succtm1ACCUMULATIONINT8Number of UMTS IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments. telemeteric subscriber category 1.VLR1MSC.M82B10C104nkmtbh, nkvsubbh
imsi_attach_umts_succtm2ACCUMULATIONINT8Number of UMTS IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments. telemeteric subscriber category 2.VLR1MSC.M82B13C104nkmtbh, nkvsubbh
imsi_attach_umts_succtm3ACCUMULATIONINT8Number of UMTS IMSI attachments. This operation is only performed when the subscriber switches the mobile phone on in the same location area where it was switched off. The SUCCESSFUL field contains only the normal subscribers IMSI attachments. telemeteric subscriber category 3.VLR1MSC.M82B16C104nkmtbh, nkvsubbh
IMSI_DETACH_SIP_ATTEMPTACCUMULATIONINT8After registration timer expires IMSI detach is carried out, that is, network initiated deregistration, or user can initiate deregistration also. It is printed only if the NVS feature is active.VLR1MSC.M82B5C109nkmtbh, nkvsubbh
imsi_detach_umts_attemptACCUMULATIONINT8Number of UMTS IMSI detachments. This operation is performed when the subscriber switches the mobile phone off.VLR1MSC.M82B5C106nkmtbh, nkvsubbh
imsi_detach_umts_attempttm1ACCUMULATIONINT8UMTS attempts of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters. telemeteric subscriber category 1.VLR1MSC.M82B10C106nkmtbh, nkvsubbh
imsi_detach_umts_attempttm2ACCUMULATIONINT8UMTS attempts of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters. telemeteric subscriber category 2.VLR1MSC.M82B13C106nkmtbh, nkvsubbh
imsi_detach_umts_attempttm3ACCUMULATIONINT8UMTS attempts of events when the SGSN initiates an explicit IMSI detach to VLR. These events are also counted to the general detach counters. telemeteric subscriber category 3.VLR1MSC.M82B16C106nkmtbh, nkvsubbh
lu_request_umts_attemptACCUMULATIONINT8Shows the total number of the requested UMTS location update attempts from A interfaceVLR1MSC.M82B7C4nkmtbh, nkvsubbh
period_ic_locreg_umts_attempttm1ACCUMULATIONINT8UMTS periodic location update attempts for all telemeteric subscribers category 1VLR1MSC.M82B8C124nkmtbh, nkvsubbh
period_ic_locreg_umts_attempttm2ACCUMULATIONINT8UMTS periodic location update attempts for all telemeteric subscribers category 2VLR1MSC.M82B11C124nkmtbh, nkvsubbh
period_ic_locreg_umts_attempttm3ACCUMULATIONINT8UMTS periodic location update attempts for all telemeteric subscribers category 3VLR1MSC.M82B14C124nkmtbh, nkvsubbh
period_ic_locreg_umts_attemptACCUMULATIONINT8UMTS periodic location update attempts for all normal subscribers.VLR1MSC.M82B3C124nkmtbh, nkvsubbh
period_ic_locreg_umts_succtm1ACCUMULATIONINT8UMTS successful periodic location updates for all telemeteric subscribers category 1VLR1MSC.M82B8C125nkmtbh, nkvsubbh
period_ic_locreg_umts_succtm2ACCUMULATIONINT8UMTS successful periodic location updatesfor all telemeteric subscribers category 2VLR1MSC.M82B11C125nkmtbh, nkvsubbh
period_ic_locreg_umts_succtm3ACCUMULATIONINT8UMTS successful periodic location updates for all telemeteric subscribers category 3VLR1MSC.M82B14C125nkmtbh, nkvsubbh
period_ic_locreg_umts_succACCUMULATIONINT8UMTS successful periodic location update attempts for all normal subscribers.VLR1MSC.M82B3C125nkmtbh, nkvsubbh
periodiclocregumtssucctm2ACCUMULATIONINT8UMTS successful periodic location updates for all telemeteric subscribers category 2VLR1MSC.M82B11C125nkmtbh, nkvsubbh


VMGW Performance Indicators

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


VMGW.Nokia.GSM.Traffic

Traffic by traffic type

KPITypeData TypeDescriptionDerivationAdditional Summaries
MGWTCAT_ANSWERED_TRAFFICERLANGINT8Shows the answered traffic in erlangs. This means that the traffic is counted from the beginning of the conversation phase (ANM/CONNECT ACK) till the end of the call (Release Complete). The field is updated at the end of the call. The value is represented in integers in the XML report and in decimal numbers in the ASCII report.MGWTCV.M395B2C14nkmgwhmbh
MGWTCAT_CALL_ATTEMPTS_ANSWERACCUMULATIONINT8The number of call attempts that were answered, that is, the CONNECT ACK or ANM message was received. This counter is updated at the same time as the CALLS counter.MGWTCV.M395B2C4nkmgwhmbh
MGWTCAT_CALL_ATTEMPTS_RINGINGACCUMULATIONINT8Shows the number of successful call attempts, which reached the ringing phase, that is, ALERTING or ACM/CON message is received. The counter is updated at the same time as the CALLS counter.MGWTCV.M395B2C3nkmgwhmbh
MGWTCAT_CALL_ATTEMPTSACCUMULATIONINT8Shows the number of call attempts. The counter is updated at the end of the call, that is, when the Release Complete message is received. A call attempt is considered only when the MGW is selected for the given category.MGWTCV.M395B2C2nkmgwhmbh
MGWTCAT_CC_GROUP1ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C5nkmgwhmbh
MGWTCAT_CC_GROUP2ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C6nkmgwhmbh
MGWTCAT_CC_GROUP3ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C7nkmgwhmbh
MGWTCAT_CC_GROUP4ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C8nkmgwhmbh
MGWTCAT_CC_GROUP5ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C9nkmgwhmbh
MGWTCAT_CC_GROUP6ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C10nkmgwhmbh
MGWTCAT_CC_GROUP7ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C11nkmgwhmbh
MGWTCAT_CC_GROUP8ACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C12nkmgwhmbh
MGWTCAT_DATA_PROV_RESTARTINTENSITYINT8Shows that the Data provider was restarted during the operation.MGWTCV.M395B3C1nkmgwhmbh
MGWTCAT_SUCC_TRAFFICACCUMULATIONINT8Shows how many call attempts are terminated in the clear code group defined in the TMH command. The field is updated at the same time as the CALLS counter.MGWTCV.M395B2C13nkmgwhmbh
MGWTCAT_TOTAL_TRAFFICERLANGINT8Shows the total traffic in erlangs. The traffic is counted from the beginning of the call till the end of the call (Release Complete) in the circuit reservation (ASSIGNMENT COMPLETE/RAB ASSIGNMENT RESPONSE/IAM). The field is updated at the end of the call. It is given in integers in the XML report and in decimal numbers in the ASCII report.MGWTCV.M395B2C15nkmgwhmbh


VMSC Performance Indicators

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


VMSC.Nokia.GSM.Call_and_Traffic

Call Traffic measurements

KPITypeData TypeDescriptionDerivationAdditional Summaries
vmsc_anstrafACCUMULATIONINT8Answer Traffic is the cumulative traffic between Answer/CONNECT ACK and Release Complete.VMSCT.M394B2C13nkmtbh
vmsc_answerACCUMULATIONINT8Number of answered call attempts. The counter is updated when the MSC Server receives the CONNECT ACK or ANSWER message.VMSCT.M394B2C3nkmtbh
vmsc_callsACCUMULATIONINT8Number of call attempts. The counter is updated in originating call case when MSC Server receives the CM_Service_request message. In a terminating case the counter is updated when MSC Sends the SETUP message, in incoming call case it is updated when the termination to the incoming side is reserved.VMSCT.M394B2C1nkmtbh
vmsc_ccgroup1ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 1VMSCT.M394B2C4nkmtbh
vmsc_ccgroup2ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 2VMSCT.M394B2C5nkmtbh
vmsc_ccgroup3ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 3VMSCT.M394B2C6nkmtbh
vmsc_ccgroup4ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 4VMSCT.M394B2C7nkmtbh
vmsc_ccgroup5ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 5VMSCT.M394B2C8nkmtbh
vmsc_ccgroup6ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 6VMSCT.M394B2C9nkmtbh
vmsc_ccgroup7ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 7VMSCT.M394B2C10nkmtbh
vmsc_ccgroup8ACCUMULATIONINT8Number of call attempts that has been terminated in the clear code group 8VMSCT.M394B2C11nkmtbh
vmsc_data_prov_restartedINTENSITYINT8If the statistics data provider program block is restarted in any of the signalling unit(s) during the period, the M394B3C1 counter is written (with value '1') under every record. Otherwise, the counter is omitted.VMSCT.M394B3C1nkmtbh
VMSC_MO_SM_ATTACCUMULATIONINT8The number of mobile-originated short message sending attempts on the given virtual MSC.VMSCT.M394B4C1nkmtbh
VMSC_MO_SM_SUCCACCUMULATIONINT8The number of mobile-originated short messages on the given virtual MSC that were successfully delivered towards the IWMSC.VMSCT.M394B4C2nkmtbh
VMSC_MT_SM_ATTACCUMULATIONINT8The number of mobile-terminated short message transaction attempts on the given virtual MSC.VMSCT.M394B4C3nkmtbh
VMSC_MT_SM_SUCCACCUMULATIONINT8The number of successful mobile-terminated short messages on the given virtual MSC.VMSCT.M394B4C4nkmtbh
vmsc_successACCUMULATIONINT8Number of successful call attempt i.e. the call has reached the ringing phase. The counter is updated when the MSC Server receives the ALERTING or ACM message.VMSCT.M394B2C2nkmtbh
vmsc_succtrafACCUMULATIONINT8Traffic is the cumulative time between Alerting and Release Complete.VMSCT.M394B2C12nkmtbh
vmsc_totrafACCUMULATIONINT8Cumulative traffic between ASSIGNMENT COMPLETE/RAB ASSIGNMENT RESPONSE/IAM and Release Complete message.VMSCT.M394B2C14nkmtbh



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:


Nokia MSC Call Setup Service Report

Report for MSC Call Setup Service data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingNo
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Bids (Mixed Line/Bar Chart)
% Successful bidsMSC.Nokia.GSM.CSSMT.%_successful_bids (Stack)User-defined 
% Unsuccessful bidsMSC.Nokia.GSM.CSSMT.%_unsuccessful_bids (Stack)User-defined 
Successful bidsMSC.Nokia.GSM.CSSMT.cssmt_succ_bids (Line)User-defined 
Unsuccessful bidsMSC.Nokia.GSM.CSSMT.cssmt_failed_bids (Line)User-defined 

Nokia MSC GSM UMTS Handover Report

Report for MSC GSM-UMTS handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
IAMSCGSMTOUMTSCLEARMSC.Nokia.GSM.GSM_UMTS_Handovers.iamscgsmtoumtsclearUser-defined 
IEPLMNIAMSCGSMTOUMTSCLEARMSC.Nokia.GSM.GSM_UMTS_Handovers.ieplmniamscgsmtoumtsclearUser-defined 
INIEMSCGSMTOUMTSCLEARMSC.Nokia.GSM.GSM_UMTS_Handovers.iniemscgsmtoumtsclearUser-defined 
INIEPLMNGSMTOUMTSCLEARMSC.Nokia.GSM.GSM_UMTS_Handovers.inieplmngsmtoumtsclearUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
OUTIEMSCGSMTOUMTSCLEARMSC.Nokia.GSM.GSM_UMTS_Handovers.outiemscgsmtoumtsclearUser-defined 
OUTIEMSCGSMTOUMTSREESTMSC.Nokia.GSM.GSM_UMTS_Handovers.outiemscgsmtoumtsreestUser-defined 
OUTIEPLMNGSMTOUMTSCLEARMSC.Nokia.GSM.GSM_UMTS_Handovers.outieplmngsmtoumtsclearUser-defined 
Region IdMSC.RegionUser-defined 
Total-dropped callsMSC.Nokia.GSM.GSM_UMTS_Handovers.dropped_callsUser-defined 
Component 2: Inter MSC (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_succ_inc_e_msc_gsm_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_unsucc_inc_e_msc_gsm_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.succ_inc_e_msc_gsm_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.unsucc_inc_e_msc_gsm_umts_ho (Line)User-defined 
Component 3: Inter MSC (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_succ_out_e_msc_gsm_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_unsucc_out_e_msc_gsm_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.succ_out_e_msc_gsm_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.unsucc_out_e_msc_gsm_umts_ho (Line)User-defined 
Component 4: Inter PLMN (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_succ_inc_e_plmn_gsm_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_unsucc_inc_e_plmn_gsm_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.succ_inc_e_plmn_gsm_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.unsucc_inc_e_plmn_gsm_umts_ho (Line)User-defined 
Component 5: Inter PLMN (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_succ_out_e_plmn_gsm_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_unsucc_out_e_plmn_gsm_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.succ_out_e_plmn_gsm_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.unsucc_out_e_plmn_gsm_umts_ho (Line)User-defined 
Component 6: Inter PLMN Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_succ_plmn_msc_gsm_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_unsucc_plmn_msc_gsm_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.succ_plmn_msc_gsm_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.unsucc_plmn_msc_gsm_umts_ho (Line)User-defined 
Component 7: Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_succ_i_msc_gsm_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.%_unsucc_i_msc_gsm_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.succ_i_msc_gsm_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.GSM_UMTS_Handovers.unsucc_i_msc_gsm_umts_ho (Line)User-defined 

Nokia MSC Handover Report

Report for MSC Handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Total Handovers (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Handover.%_succ_ho_total (Bar)User-defined 
SuccessfulMSC.Nokia.GSM.Handover.succ_ho_total (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Handover.unsucc_ho_total (Line)User-defined 

Nokia MSC Simultaneous Calls Report

Report for MSC Simultaneous Calls Report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, MSC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Simultaneous Calls (Table)
SIMUL_MSC_AVG_SIM_CALLMSC.Nokia.GSM.Simultaneous_Calls.SIMUL_MSC_AVG_SIM_CALLUser-defined 
SIMUL_MSC_PEAK_SIM_CALLMSC.Nokia.GSM.Simultaneous_Calls.SIMUL_MSC_PEAK_SIM_CALLUser-defined 
MSC_IdMSC.idUser-defined 
Region_IdMSC.RegionUser-defined 

Nokia NSS BSS Handover Report

Report for handover data at BSC/RNC level.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.BSC
Primary ObjectBSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionBSC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Handovers - BSC/RNC (Table)
BSC IDBSC.idUser-defined 
BSC NameBSC.nameUser-defined 
MSC IDBSC.MSCUser-defined 
MSC to BSC NOKBSC.Nokia.GSM.Handover.from_other_msc_to_bsc_nokUser-defined 
MSC to BSC OKBSC.Nokia.GSM.Handover.from_other_msc_to_bsc_okUser-defined 
MSC to RNC NOKBSC.Nokia.GSM.Handover.from_other_msc_to_rnc_nokUser-defined 
MSC to RNC OKBSC.Nokia.GSM.Handover.from_other_msc_to_rnc_okUser-defined 
Region IDBSC.RegionUser-defined 
Component 2: Handovers - Neighbour BSC/RNC (Table)
BSC IDBSC.idUser-defined 
BSC NameBSC.nameUser-defined 
BSC from NOKBSC.Nokia.GSM.Handover.neighbour_bsc_from_nokUser-defined 
BSC from OKBSC.Nokia.GSM.Handover.neighbour_bsc_from_okUser-defined 
BSC to NOKBSC.Nokia.GSM.Handover.neighbour_bsc_to_nokUser-defined 
BSC to OKBSC.Nokia.GSM.Handover.neighbour_bsc_to_okUser-defined 
MSC IDBSC.MSCUser-defined 
RNC from NOKBSC.Nokia.GSM.Handover.neighbour_rnc_from_nokUser-defined 
RNC from OKBSC.Nokia.GSM.Handover.neighbour_rnc_from_okUser-defined 
RNC to NOKBSC.Nokia.GSM.Handover.neighbour_rnc_to_nokUser-defined 
RNC to OKBSC.Nokia.GSM.Handover.neighbour_rnc_to_okUser-defined 
Region IDBSC.RegionUser-defined 

Nokia NSS Cell MSC Handover Report

Report for cell level MSC handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Cell
Primary ObjectCell
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionCell
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Handovers (Table)
Cell IdCell.idUser-defined 
Cell NameCell.nameUser-defined 
From neighbour NOKCell.Nokia.GSM.MSC_Handover_Cell.fromneighbourcellnokUser-defined 
From neighbour OKCell.Nokia.GSM.MSC_Handover_Cell.fromneighbourcellokUser-defined 
MSC IdCell.MSCUser-defined 
Region IdCell.RegionUser-defined 
Successful adjacentCell.Nokia.GSM.MSC_Handover_Cell.succ_to_adjac_cell_hoUser-defined 
Successful intracellCell.Nokia.GSM.MSC_Handover_Cell.intra_cell_okUser-defined 
To neighbour NOKCell.Nokia.GSM.MSC_Handover_Cell.toneighbourcellnokUser-defined 

Nokia NSS D Link Traffic Report

Report for transmitted and received octets and frames for D-Links.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.D_Link
Primary ObjectD_Link
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, D_Link
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Octets and Frames TX/RX (Table)
D LINK IDD_Link.idUser-defined 
D LINK NameD_Link.nameUser-defined 
MSC IdD_Link.MSCUser-defined 
RX I frame octetsD_Link.Nokia.GSM.Traffic.received_i_octetsUser-defined 
RX I framesD_Link.Nokia.GSM.Traffic.received_i_framesUser-defined 
RX UI frame octetD_Link.Nokia.GSM.Traffic.received_ui_octetsUser-defined 
RX UI framesD_Link.Nokia.GSM.Traffic.received_ui_framesUser-defined 
RX total frame octetsD_Link.Nokia.GSM.Traffic.received_total_octetsUser-defined 
Region IdD_Link.RegionUser-defined 
TX I frame octetsD_Link.Nokia.GSM.Traffic.trans_i_octetsUser-defined 
TX I framesD_Link.Nokia.GSM.Traffic.trans_i_framesUser-defined 
TX UI frame octetsD_Link.Nokia.GSM.Traffic.trans_ui_octetsUser-defined 
TX UI framesD_Link.Nokia.GSM.Traffic.trans_ui_framesUser-defined 
TX total frame octetsD_Link.Nokia.GSM.Traffic.trans_total_octetsUser-defined 
Total octetsD_Link.Nokia.GSM.Traffic.total_octetsUser-defined 

Nokia NSS EIR Listed Devices Report

Report for black/grey/white listed devices

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Black_List (Table)
Black list requestsHLR.Nokia.GSM.EIR.tot_black_reqUser-defined 
HLR IdHLR.idUser-defined 
HLR NameHLR.nameUser-defined 
Region IdHLR.RegionUser-defined 
Total black entriesHLR.Nokia.GSM.EIR.tot_black_entriesUser-defined 
Component 2: Grey_List (Table)
Grey list requestsHLR.Nokia.GSM.EIR.tot_grey_reqUser-defined 
HLR IdHLR.idUser-defined 
HLR NameHLR.nameUser-defined 
Region IdHLR.RegionUser-defined 
Total grey entriesHLR.Nokia.GSM.EIR.tot_grey_entriesUser-defined 
Component 3: White_List (Table)
HLR IdHLR.idUser-defined 
HLR NameHLR.nameUser-defined 
Region IdHLR.RegionUser-defined 
Total white entriesHLR.Nokia.GSM.EIR.tot_unknown_reqUser-defined 
White list requestsHLR.Nokia.GSM.EIR.tot_white_reqUser-defined 

Nokia NSS HLR_Destination INAP App Context

INAP Application Contexts Report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR_Destination
Primary ObjectHLR_Destination
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, Network, HLR, HLR_Destination
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_HLR_Subscribers_Busy_Hour, Average, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: INAP Application Contexts Report (Table)
%_INAP_IAC_SUCCEEDEDHLR_Destination.Nokia.GSM.Incoming_INAP_Application_Context.%_INAP_IAC_SUCCEEDEDUser-defined 
%_INAP_OAC_SUCCEEDEDHLR_Destination.Nokia.GSM.Outgoing_INAP_Application_Context.%_INAP_OAC_SUCCEEDEDUser-defined 
INAP_IAC_SUM_FAILEDHLR_Destination.Nokia.GSM.Incoming_INAP_Application_Context.INAP_IAC_SUM_FAILEDUser-defined 
INAP_IAC_SUM_STARTEDHLR_Destination.Nokia.GSM.Incoming_INAP_Application_Context.INAP_IAC_SUM_STARTEDUser-defined 
INAP_IAC_SUM_SUCCEEDEDHLR_Destination.Nokia.GSM.Incoming_INAP_Application_Context.INAP_IAC_SUM_SUCCEEDEDUser-defined 
INAP_OAC_SUM_FAILEDHLR_Destination.Nokia.GSM.Outgoing_INAP_Application_Context.INAP_OAC_SUM_FAILEDUser-defined 
INAP_OAC_SUM_STARTEDHLR_Destination.Nokia.GSM.Outgoing_INAP_Application_Context.INAP_OAC_SUM_STARTEDUser-defined 
INAP_OAC_SUM_SUCCEEDEDHLR_Destination.Nokia.GSM.Outgoing_INAP_Application_Context.INAP_OAC_SUM_SUCCEEDEDUser-defined 
HLR_Destination_IdHLR_Destination.idUser-defined 
HLR_Destination_NameHLR_Destination.nameUser-defined 
HLR_IdHLR_Destination.HLRUser-defined 

Nokia NSS HLR_Destination INAP Detection Point

INAP Detection Point Report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR_Destination
Primary ObjectHLR_Destination
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, Network, HLR, HLR_Destination
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_HLR_Subscribers_Busy_Hour, Average, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: INAP Service Invocations (Table)
INAP_DP_SUM_STARTEDHLR_Destination.Nokia.GSM.INAP_Invocation.INAP_DP_SUM_STARTEDUser-defined 
HLR_Destination_IdHLR_Destination.idUser-defined 
HLR_Destination_NameHLR_Destination.nameUser-defined 
HLR_IdHLR_Destination.HLRUser-defined 

Nokia NSS HLR Authentication Count Report

Report detailing data from the Authentication_count KPI group. Secondary key of VLR_Address.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR, VLR_Address
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Authentication Requests Chart (Line Chart)
Triplets answeredHLR.Nokia.GSM.Authentication_Count.nbr_ansUser-defined 
Triplets requestedHLR.Nokia.GSM.Authentication_Count.nbr_reqUser-defined 
Component 2: Authentication Requests Table (Table)
1)HLR IdHLR.idUser-defined 
2)HLR NameHLR.nameUser-defined 
3)Region IdHLR.RegionUser-defined 
4)Triplets requestedHLR.Nokia.GSM.Authentication_Count.nbr_reqUser-defined 
5)Triplets answeredHLR.Nokia.GSM.Authentication_Count.nbr_ansUser-defined 
7)Total quintetsHLR.Nokia.GSM.Authentication_Count.number_of_syncreqUser-defined 
8)SyncreqHLR.Nokia.GSM.Authentication_Count.nbr_triplUser-defined 

Nokia NSS HLR Authentication Report

Report for data from the Authentication Report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Authentication Requests Chart (Line Chart)
Triplets answeredHLR.Nokia.GSM.Authentication_nknss.tot_nbr_ansUser-defined 
Triplets requestedHLR.Nokia.GSM.Authentication_nknss.tot_nbr_reqUser-defined 
Component 2: Authentication Requests Table (Table)
1)HLR IdHLR.idUser-defined 
2)HLR NameHLR.nameUser-defined 
3)Region IdHLR.RegionUser-defined 
4)Triplets RequestedHLR.Nokia.GSM.Authentication_nknss.tot_nbr_reqUser-defined 
5)Triplets AnsweredHLR.Nokia.GSM.Authentication_nknss.tot_nbr_ansUser-defined 
6)Total TripletsHLR.Nokia.GSM.Authentication_nknss.tot_nbr_triplUser-defined 

Nokia NSS HLR GPRS Subscriber Report

Report for GPRS subscriber data at the HLR object level.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Subscribers Chart (Line Chart)
Average subscribersHLR.Nokia.GSM.GPRS_Subscribers.average_nbr_of_subscribers_sgsnUser-defined 
Current subscribersHLR.Nokia.GSM.GPRS_Subscribers.current_nbr_of_subscribers_sgsnUser-defined 
Component 2: Subscribers Table (Table)
Average subscribersHLR.Nokia.GSM.GPRS_Subscribers.average_nbr_of_subscribers_sgsnUser-defined 
Current subscribersHLR.Nokia.GSM.GPRS_Subscribers.current_nbr_of_subscribers_sgsnUser-defined 
HLR IdHLR.idUser-defined 
HLR NameHLR.nameUser-defined 
Region IdHLR.RegionUser-defined 

Nokia NSS HLR Mobility Report

Report for HLR Mobility data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: PLMN_Visits (Line Chart)
Successful PLMN visitsHLR.Nokia.GSM.Mobility.succ_home_visitsUser-defined 
Successful returnsHLR.Nokia.GSM.Mobility.succ_home_retUser-defined 
Component 2: Subscriber_LU (Line Chart)
Successful LUHLR.Nokia.GSM.Mobility.tot_succ_home_luUser-defined 
Unsuccessful LUHLR.Nokia.GSM.Mobility.tot_fail_home_luUser-defined 

Nokia NSS HLR MultiSIM Mobility Report

Report for MultiSIM HLR Mobility data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, HLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_HLR_Subscribers_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MultiSIM Report (Table)
ATI_MULTISIM_GROUP_SUCCHLR.Nokia.GSM.Mobility.ATI_MULTISIM_GROUP_SUCCUser-defined 
GPRS_GROUP_MEM_ATTHLR.Nokia.GSM.Mobility.GPRS_GROUP_MEMBERS_ATTEMPTUser-defined 
GPRS_GROUP_MEM_SUCCHLR.Nokia.GSM.Mobility.GPRS_GROUP_MEMBERS_SUCCUser-defined 
HOME_SUBS_GRP_MEM_FAILHLR.Nokia.GSM.Mobility.HOME_SUBS_GROUP_MEMBERS_FAILUser-defined 
HOME_SUBS_GRP_MEM_SUCCHLR.Nokia.GSM.Mobility.HOME_SUBS_GROUP_MEMBERS_SUCCUser-defined 
PSI_MULTISIM_GROUP_ATTHLR.Nokia.GSM.Mobility.PSI_MULTISIM_GROUP_ATTEMPTUser-defined 
PSI_MULTISIM_GROUP_SUCCHLR.Nokia.GSM.Mobility.PSI_MULTISIM_GROUP_SUCCUser-defined 
SYNCH_TO_GROUP_FAILEDHLR.Nokia.GSM.Mobility.SYNCHRONIZED_TO_GROUP_FAILEDUser-defined 
SYNCH_TO_GROUP_SUCCHLR.Nokia.GSM.Mobility.SYNCHRONIZED_TO_GROUP_SUCCUser-defined 
HLR_IdHLR.idUser-defined 
HLR_NameHLR.nameUser-defined 
ATI_MULTISIM_GROUP_ATTHLR.Nokia.GSM.Mobility.ATI_MULTISIM_GROUP_ATTEMPTUser-defined 

Nokia NSS HLR SCCP Single Meter Report

Report for HLR SCCP message data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SCCP_messages (Line Chart)
From local subsystemHLR.Nokia.GSM.SCCP_Single_Meter.sccp_from_localUser-defined 
To local subsystemHLR.Nokia.GSM.SCCP_Single_Meter.sccp_to_localUser-defined 
Total messagesHLR.Nokia.GSM.SCCP_Single_Meter.sccp_totalUser-defined 

Nokia NSS HLR Subscribers in VLR Report

Report for HLR subscribers in VLR data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.HLR
Primary ObjectHLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionHLR, VLR_Address
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Subscribers in VLR (Line Chart)
Average subscribersHLR.Nokia.GSM.Subscribers_in_VLR.ave_subsc_in_vlrUser-defined 
SubscribersHLR.Nokia.GSM.Subscribers_in_VLR.subsc_in_vlrUser-defined 

Nokia NSS Interface_LAN Unit Errors

Interface_LAN Unit Error Report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Interface_LAN
Primary ObjectInterface_LAN
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, Network, Computer_Unit, Interface_LAN, PIU
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_Interface_LAN_Packet_Traffic_Busy_Hour, Average, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Packet Errors (Table)
COLLISIONSInterface_LAN.Nokia.GSM.LAN_Unit_Error.COLLISIONSUser-defined 
CRC_ALIGN_ERRORSInterface_LAN.Nokia.GSM.LAN_Unit_Error.CRC_ALIGN_ERRORSUser-defined 
FIFO_OVERRUNInterface_LAN.Nokia.GSM.LAN_Unit_Error.FIFO_OVERRUNUser-defined 
LINE_NOT_READYInterface_LAN.Nokia.GSM.LAN_Unit_Error.LINE_NOT_READYUser-defined 
OVERSIZE_PACKETSInterface_LAN.Nokia.GSM.LAN_Unit_Error.OVERSIZE_PACKETSUser-defined 
RECEIVED_PAUSE_OFF_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Error.RECEIVED_PAUSE_OFF_PACKETSUser-defined 
RECEIVED_PAUSE_ON_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Error.RECEIVED_PAUSE_ON_PACKETSUser-defined 
TRANSMITTED_PAUSE_OFF_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Error.TRANSMITTED_PAUSE_OFF_PACKETSUser-defined 
TRANSMITTED_PAUSE_ON_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Error.TRANSMITTED_PAUSE_ON_PACKETSUser-defined 
UNDERSIZE_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Error.UNDERSIZE_PACKETSUser-defined 
UNKNOWN_SAP_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Error.UNKNOWN_SAP_PACKETSUser-defined 
Interface_LAN_IdInterface_LAN.idUser-defined 
PIU_idInterface_LAN.PIUUser-defined 
Unit_idInterface_LAN.UnitUser-defined 

Nokia NSS Interface_LAN Unit Traffic

Interface_LAN Unit Traffic Report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Interface_LAN
Primary ObjectInterface_LAN
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, Network, Computer_Unit, Interface_LAN, PIU
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_Interface_LAN_Packet_Traffic_Busy_Hour, Average, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Packet Traffic (Table)
RXED_AVG_UTIL_RATEInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic.RECEIVED_AVG_UTIL_RATEUser-defined 
RXED_BROADCAST_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic.RECEIVED_BROADCAST_PACKETSUser-defined 
RXED_MULTI_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic.RECEIVED_MULTI_PACKETSUser-defined 
RXED_OCTETSInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic.RECEIVED_OCTETSUser-defined 
RXED_PEAK_UTIL_RATEInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic.RECEIVED_PEAK_UTIL_RATEUser-defined 
TXED_AVG_UTIL_RATEInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic.TRANSMITTED_AVG_UTIL_RATEUser-defined 
TXED_BROADCAST_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic.TRANSMITTED_BROADCAST_PACKETSUser-defined 
TXED_MULTI_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic.TRANSMITTED_MULTI_PACKETSUser-defined 
TXED_OCTETSInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic.TRANSMITTED_OCTETSUser-defined 
TXED_PEAK_UTIL_RATEInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic.TRANSMITTED_PEAK_UTIL_RATEUser-defined 
Interface_LAN_IdInterface_LAN.idUser-defined 
PIU_idInterface_LAN.PIUUser-defined 
Unit_idInterface_LAN.UnitUser-defined 
TOTAL_TX_AND_RX_PKTSInterface_LAN.Nokia.GSM.LAN_Unit_Utilisation.TOTAL_TX_AND_RX_PACKETSUser-defined 
RXED_PKSInterface_LAN.Nokia.GSM.LAN_Unit_Received_Traffic.RECEIVED_PACKETSUser-defined 
TXED_PKSInterface_LAN.Nokia.GSM.LAN_Unit_Transmit_Traffic.TRANSMITTED_PACKETSUser-defined 

Nokia NSS Interface_MAP Operations

Nokia NSS Interface_MAP Operations

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Interface_MAP
Primary ObjectInterface_MAP
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, Network, Interface_MAP
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_IMAP_Operations_Incoming_Outgoing_Busy_Hour, Average, Total
FilteringInterface_MAP.Nokia.GSM.Outgoing_Operation_Part2.%_MAP_O_OC_2_SUCCEEDED_OCS (min/max)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Incoming and Outgoing Operations (Table)
%_MAP_I_OC_2_SUCCEEDED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part2.%_MAP_I_OC_2_SUCCEEDED_OCSUser-defined 
%_MAP_O_OC_2_SUCCEEDED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part2.%_MAP_O_OC_2_SUCCEEDED_OCSUser-defined 
MAP_I_OC_1_SUM_FAILED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part1.MAP_I_OC_1_SUM_FAILED_OCSUser-defined 
MAP_I_OC_1_SUM_STARTED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part1.MAP_I_OC_1_SUM_STARTED_OCSUser-defined 
MAP_I_OC_1_SUM_SUCCEEDED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part1.MAP_I_OC_1_SUM_SUCCEEDED_OCSUser-defined 
MAP_I_OC_2_SUM_FAILED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part2.MAP_I_OC_2_SUM_FAILED_OCSUser-defined 
MAP_I_OC_2_SUM_STARTED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part2.MAP_I_OC_2_SUM_STARTED_OCSUser-defined 
MAP_I_OC_2_SUM_SUCCEEDED_OCSInterface_MAP.Nokia.GSM.Incoming_Operation_Part2.MAP_I_OC_2_SUM_SUCCEEDED_OCSUser-defined 
MAP_O_OC_1_SUM_FAILED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_O_OC_1_SUM_FAILED_OCSUser-defined 
MAP_O_OC_1_SUM_STARTED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_O_OC_1_SUM_STARTED_OCSUser-defined 
MAP_O_OC_1_SUM_SUCCEEDED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_O_OC_1_SUM_SUCCEEDED_OCSUser-defined 
MAP_O_OC_2_SUM_FAILED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part2.MAP_O_OC_2_SUM_FAILED_OCSUser-defined 
MAP_O_OC_2_SUM_STARTED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part2.MAP_O_OC_2_SUM_STARTED_OCSUser-defined 
MAP_O_OC_2_SUM_SUCCEEDED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part2.MAP_O_OC_2_SUM_SUCCEEDED_OCSUser-defined 
MAP_TOTAL_I_O_STARTED_OCSInterface_MAP.Nokia.GSM.Outgoing_Operation_Part1.MAP_TOTAL_I_O_STARTED_OCSUser-defined 
Interface_MAP_IdInterface_MAP.idUser-defined 
Region_IdInterface_MAP.RegionUser-defined 

Nokia NSS Inter VLR GSM Report

Report for inter-vlr data

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_VLR_Subscribers_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Location Updates (home subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Inter_VLR_GSM.%_intervlrhsgsmsucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Inter_VLR_GSM.intervlrhsgsmattempt (Line)User-defined 
SuccessfulVLR.Nokia.GSM.Inter_VLR_GSM.intervlrhsgsmsucc (Line)User-defined 
Component 2: Location Updates (visiting subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Inter_VLR_GSM.%_intervlrrsgsmsucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Inter_VLR_GSM.intervlrrsgsmattempt (Line)User-defined 
SuccessfulVLR.Nokia.GSM.Inter_VLR_GSM.intervlrrsgsmsucc (Line)User-defined 

Nokia NSS Inter VLR UMTS Report

Report for inter-vlr UMTS data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_VLR_Subscribers_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Location Updates (home subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Inter_VLR_UMTS.%_inter_vlr_hs_umts_succ (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_hs_umts_attempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_hs_umts_succ (Line)User-defined 
Component 2: Location Updates (visiting subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Inter_VLR_UMTS.%_inter_vlr_rs_umts_succ (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_rs_umts_attempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Inter_VLR_UMTS.inter_vlr_rs_umts_succ (Line)User-defined 

Nokia NSS Intra VLR GSM

Report from Intra VLR GSM data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Location Updates Inter PLMN (home subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_GSM.%_intravlrinterplmnhsgsmsucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnhsgsmattempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnhsgsmsucc (Line)User-defined 
Component 2: Location Updates Inter PLMN (visiting subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_GSM.%_intravlrinterplmnrsgsmsucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnrsgsmattempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_GSM.intravlrinterplmnrsgsmsucc (Line)User-defined 
Component 3: Location Updates Intra PLMN (home subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_GSM.%_intravlrintraplmnhsgsmsucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnhsgsmattempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnhsgsmsucc (Line)User-defined 
Component 4: Location Updates Intra PLMN (visiting subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_GSM.%_intravlrintraplmnrsgsmsucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnrsgsmattempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_GSM.intravlrintraplmnrsgsmsucc (Line)User-defined 

Nokia NSS Intra VLR UMTS

Report for intra-VLR UMTS data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Location Updates Inter PLMN (home subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_UMTS.%_intra_vlr_inter_plmn_hs_umts_succ (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_hs_umts_attempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_hs_umts_succ (Line)User-defined 
Component 2: Location Updates Inter PLMN (visiting subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_UMTS.%_intra_vlr_inter_plmn_rs_umts_succ (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_rs_umts_attempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_inter_plmn_rs_umts_succ (Line)User-defined 
Component 3: Location Updates Intra PLMN (home subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_UMTS.%_intravlrintraplmnhsumtssucc (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_UMTS.intravlrintraplmnhsumtsattempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_UMTS.intravlrintraplmnhsumtssucc (Line)User-defined 
Component 4: Location Updates Intra PLMN (visiting subscribers) (Mixed Line/Bar Chart)
% Successful LUVLR.Nokia.GSM.Intra_VLR_UMTS.%_intra_vlr_intra_plmn_rs_umts_succ (Stack)User-defined 
AttemptsVLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_intra_plmn_rs_umts_attempt (Line)User-defined 
SuccessesVLR.Nokia.GSM.Intra_VLR_UMTS.intra_vlr_intra_plmn_rs_umts_succ (Line)User-defined 

Nokia NSS IP ATM Traffic Report

Report for MGW IP and ATM traffic data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MGW
Primary ObjectMGW
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMGW
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: AAL1 (Table)
% Successful callsMGW.Nokia.GSM.IP_ATM_traffic.%_successful_aal1_callsUser-defined 
Attempts callsMGW.Nokia.GSM.IP_ATM_traffic.aal1_call_amountUser-defined 
Congested callsMGW.Nokia.GSM.IP_ATM_traffic.aal1_congested_fcallsUser-defined 
Failed callsMGW.Nokia.GSM.IP_ATM_traffic.aal1_failed_callsUser-defined 
MGW IdMGW.idUser-defined 
MGW NameMGW.nameUser-defined 
Region IdMGW.RegionUser-defined 
Successful callsMGW.Nokia.GSM.IP_ATM_traffic.aal1_success_callsUser-defined 
Component 2: AAL2 (Table)
% Successful callsMGW.Nokia.GSM.IP_ATM_traffic.%_successful_aal2_callsUser-defined 
Attempts callsMGW.Nokia.GSM.IP_ATM_traffic.aal2_call_amountUser-defined 
Congested callsMGW.Nokia.GSM.IP_ATM_traffic.aal2_congested_fcallsUser-defined 
Failed callsMGW.Nokia.GSM.IP_ATM_traffic.aal2_failed_callsUser-defined 
MGW IdMGW.idUser-defined 
MGW NameMGW.nameUser-defined 
Region IdMGW.RegionUser-defined 
Successful callsMGW.Nokia.GSM.IP_ATM_traffic.aal2_success_callsUser-defined 
Component 3: IP (Table)
% Successful callsMGW.Nokia.GSM.IP_ATM_traffic.%_successful_ip_callsUser-defined 
Attempts callsMGW.Nokia.GSM.IP_ATM_traffic.ip_call_amountUser-defined 
Congested callsMGW.Nokia.GSM.IP_ATM_traffic.ip_congested_fcallsUser-defined 
Failed callsMGW.Nokia.GSM.IP_ATM_traffic.ip_failed_callsUser-defined 
MGW IdMGW.idUser-defined 
MGW NameMGW.nameUser-defined 
Region IdMGW.RegionUser-defined 
Successful callsMGW.Nokia.GSM.IP_ATM_traffic.ip_success_callsUser-defined 
Component 4: IPv6 (Table)
% Successful callsMGW.Nokia.GSM.IP_ATM_traffic.%_successful_ipv6_callsUser-defined 
Attempts callsMGW.Nokia.GSM.IP_ATM_traffic.ipv6_call_amountUser-defined 
Congested callsMGW.Nokia.GSM.IP_ATM_traffic.ipv6_congested_fcallsUser-defined 
Failed callsMGW.Nokia.GSM.IP_ATM_traffic.ipv6_failed_callsUser-defined 
MGW IdMGW.idUser-defined 
MGW NameMGW.nameUser-defined 
Region IdMGW.RegionUser-defined 
Successful callsMGW.Nokia.GSM.IP_ATM_traffic.ipv6_success_callsUser-defined 

Nokia NSS LAC Paging Report

Report for LAC paging data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.LAC
Primary ObjectLAC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionLAC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Paging (Table)
Answer timeLAC.Nokia.GSM.Paging.answer_timeUser-defined 
Attempts imsi failLAC.Nokia.GSM.Paging.paging_attempt_with_imsifailUser-defined 
Attempts perLaLAC.Nokia.GSM.Paging.paging_attempt_perlaUser-defined 
Attempts tmsi failLAC.Nokia.GSM.Paging.paging_attempt_with_tmsifailUser-defined 
LAC IdLAC.idUser-defined 
LAC NameLAC.nameUser-defined 
MSC IdLAC.MSCUser-defined 
Region IdLAC.RegionUser-defined 
Successful imsi failLAC.Nokia.GSM.Paging.paging_attempt_with_imsisuccUser-defined 
Successful perLaLAC.Nokia.GSM.Paging.paging_succ_perlaUser-defined 
Successful tmsi failLAC.Nokia.GSM.Paging.paging_attempt_with_tmsisuccUser-defined 

Nokia NSS LAC Subscriber Report

Report for VLR LAC subscriber data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.LAC
Primary ObjectLAC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionLAC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Subscribers (Line Chart)
Average subscribersLAC.Nokia.GSM.VLR_LAC.ave_subsc_in_laUser-defined 
SubscribersLAC.Nokia.GSM.VLR_LAC.subsc_in_laUser-defined 

Nokia NSS MAP Application Contexts

Nokia NSS Outgoing Application Contexts

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Interface_MAP
Primary ObjectInterface_MAP
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRegion, Network, Interface_MAP
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_IMAP_Operations_Incoming_Outgoing_Busy_Hour, Average, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Outgoing and Incoming Application Contexts (Table)
MAP_I_AC_1_SUM_FAILED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part1.MAP_I_AC_1_SUM_FAILED_ACSUser-defined 
MAP_I_AC_1_SUM_STARTED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part1.MAP_I_AC_1_SUM_STARTED_ACSUser-defined 
MAP_I_AC_1_SUM_SUCCEEDED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part1.MAP_I_AC_1_SUM_SUCCEEDED_ACSUser-defined 
MAP_I_AC_2_SUM_FAILED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part2.MAP_I_AC_2_SUM_FAILED_ACSUser-defined 
MAP_I_AC_2_SUM_STARTED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part2.MAP_I_AC_2_SUM_STARTED_ACSUser-defined 
MAP_I_AC_2_SUM_SUCCEEDED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part2.MAP_I_AC_2_SUM_SUCCEEDED_ACSUser-defined 
MAP_I_AC_3_SUM_FAILED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part3.MAP_I_AC_3_SUM_FAILED_ACSUser-defined 
MAP_I_AC_3_SUM_STARTED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part3.MAP_I_AC_3_SUM_STARTED_ACSUser-defined 
MAP_I_AC_3_SUM_SUCCEEDED_ACSInterface_MAP.Nokia.GSM.Incoming_App_Context_Part3.MAP_I_AC_3_SUM_SUCCEEDED_ACSUser-defined 
MAP_O_AC_1_SUM_FAILED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part1.MAP_O_AC_1_SUM_FAILED_ACSUser-defined 
MAP_O_AC_1_SUM_STARTED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part1.MAP_O_AC_1_SUM_STARTED_ACSUser-defined 
MAP_O_AC_1_SUM_SUCCEEDED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part1.MAP_O_AC_1_SUM_SUCCEEDED_ACSUser-defined 
MAP_O_AC_2_SUM_FAILED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part2.MAP_O_AC_2_SUM_FAILED_ACSUser-defined 
MAP_O_AC_2_SUM_STARTED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part2.MAP_O_AC_2_SUM_STARTED_ACSUser-defined 
MAP_O_AC_2_SUM_SUCCEEDED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part2.MAP_O_AC_2_SUM_SUCCEEDED_ACSUser-defined 
MAP_O_AC_3_SUM_FAILED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part3.MAP_O_AC_3_SUM_FAILED_ACSUser-defined 
MAP_O_AC_3_SUM_STARTED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part3.MAP_O_AC_3_SUM_STARTED_ACSUser-defined 
MAP_O_AC_3_SUM_SUCCEEDED_ACSInterface_MAP.Nokia.GSM.Outgoing_App_Context_Part3.MAP_O_AC_3_SUM_SUCCEEDED_ACSUser-defined 
Interface_MAP_IdInterface_MAP.idUser-defined 
Region_IdInterface_MAP.RegionUser-defined 

Nokia NSS MGW Handover Report

Report for MGW handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MGW
Primary ObjectMGW
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMGW
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MGW_Incoming_Request_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Handovers (Table)
From neighbour NOKMGW.Nokia.GSM.Handover.from_neighbour_mgw_nokUser-defined 
From neighbour OKMGW.Nokia.GSM.Handover.from_neighbour_mgw_okUser-defined 
From other NOKMGW.Nokia.GSM.Handover.otherlegacybscrncfromnokUser-defined 
From other OKMGW.Nokia.GSM.Handover.otherlegacybscrncfromokUser-defined 
MGW IdMGW.idUser-defined 
MGW NameMGW.nameUser-defined 
Region IdMGW.RegionUser-defined 
To neighbour NOKMGW.Nokia.GSM.Handover.toneighbourmgwnokUser-defined 
To neighbour OKMGW.Nokia.GSM.Handover.toneighbourmgwokUser-defined 
To other NOKMGW.Nokia.GSM.Handover.otherlegacybscrnctonokUser-defined 
To other OKMGW.Nokia.GSM.Handover.otherlegacybscrnctookUser-defined 

Nokia NSS MGW UPD Traffic Report

Report for MGW user plane destination traffic.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MGW
Primary ObjectMGW
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMGW
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MGW_Incoming_Request_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Traffic (Line Chart)
TrafficMGW.Nokia.GSM.UPD.upd_erlangs_x100User-defined 

Nokia NSS MSC_Destination CAP Operations

CAP Operations report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC_Destination
Primary ObjectMSC_Destination
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, MSC_Destination
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Total
FilteringMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3.%_SUCC_CAP_IOC_TOTAL (min/max)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: CAP Operations (Table)
%_CAP_OOC_SUCCMSC_Destination.Nokia.GSM.Outgoing_CAP_Operation.%_CAP_OOC_SUCCEEDEDUser-defined 
%_SUCC_CAP_IOC_TOTALMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3.%_SUCC_CAP_IOC_TOTALUser-defined 
CAP_IOC1_SUM_FAILEDMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1.CAP_IOC1_SUM_FAILEDUser-defined 
CAP_IOC1_SUM_STARTEDMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1.CAP_IOC1_SUM_STARTEDUser-defined 
CAP_IOC1_SUM_SUCCMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part1.CAP_IOC1_SUM_SUCCEEDEDUser-defined 
CAP_IOC2_SUM_FAILEDMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2.CAP_IOC2_SUM_FAILEDUser-defined 
CAP_IOC2_SUM_STARTEDMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2.CAP_IOC2_SUM_STARTEDUser-defined 
CAP_IOC2_SUM_SUCCMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part2.CAP_IOC2_SUM_SUCCEEDEDUser-defined 
CAP_IOC3_SUM_FAILEDMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3.CAP_IOC3_SUM_FAILEDUser-defined 
CAP_IOC3_SUM_STARTEDMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3.CAP_IOC3_SUM_STARTEDUser-defined 
CAP_IOC3_SUM_SUCCMSC_Destination.Nokia.GSM.Incoming_CAP_Operations_Part3.CAP_IOC3_SUM_SUCCEEDEDUser-defined 
CAP_OOC_SUM_FAILEDMSC_Destination.Nokia.GSM.Outgoing_CAP_Operation.CAP_OOC_SUM_FAILEDUser-defined 
CAP_OOC_SUM_STARTEDMSC_Destination.Nokia.GSM.Outgoing_CAP_Operation.CAP_OOC_SUM_STARTEDUser-defined 
CAP_OOC_SUM_SUCCMSC_Destination.Nokia.GSM.Outgoing_CAP_Operation.CAP_OOC_SUM_SUCCEEDEDUser-defined 
MSC_Destination_IdMSC_Destination.idUser-defined 
MSC_IdMSC_Destination.MSCUser-defined 

Nokia NSS MSC_Destination INAP Operations

INAP Operations report

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC_Destination
Primary ObjectMSC_Destination
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, MSC_Destination
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: INAP Operations (Table)
%_INAP_OOC_SUCCEEDEDMSC_Destination.Nokia.GSM.INAP_Outgoing_Op_Code.%_INAP_OOC_SUCCEEDEDUser-defined 
%_SSAP_OC_SUCCEEDED_OUTMSC_Destination.Nokia.GSM.SSAP_Operation_Code.%_SSAP_OC_SUCCEEDED_OUTUser-defined 
INAP_IOC1_SUM_STARTEDMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part1.INAP_IOC1_SUM_STARTEDUser-defined 
INAP_IOC1_SUM_SUCCEEDEDMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part1.INAP_IOC1_SUM_SUCCEEDEDUser-defined 
INAP_IOC2_SUM_FAILEDMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part2.INAP_IOC2_SUM_FAILEDUser-defined 
INAP_IOC2_SUM_STARTEDMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part2.INAP_IOC2_SUM_STARTEDUser-defined 
INAP_IOC2_SUM_SUCCEEDEDMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part2.INAP_IOC2_SUM_SUCCEEDEDUser-defined 
INAP_OOC_SUM_FAILEDMSC_Destination.Nokia.GSM.INAP_Outgoing_Op_Code.INAP_OOC_SUM_FAILEDUser-defined 
INAP_OOC_SUM_STARTEDMSC_Destination.Nokia.GSM.INAP_Outgoing_Op_Code.INAP_OOC_SUM_STARTEDUser-defined 
INAP_OOC_SUM_SUCCEEDEDMSC_Destination.Nokia.GSM.INAP_Outgoing_Op_Code.INAP_OOC_SUM_SUCCEEDEDUser-defined 
SSAP_OC_SUM_FAILED_INMSC_Destination.Nokia.GSM.SSAP_Operation_Code.SSAP_OC_SUM_FAILED_INUser-defined 
SSAP_OC_SUM_FAILED_OUTMSC_Destination.Nokia.GSM.SSAP_Operation_Code.SSAP_OC_SUM_FAILED_OUTUser-defined 
SSAP_OC_SUM_STARTED_INMSC_Destination.Nokia.GSM.SSAP_Operation_Code.SSAP_OC_SUM_STARTED_INUser-defined 
SSAP_OC_SUM_STARTED_OUTMSC_Destination.Nokia.GSM.SSAP_Operation_Code.SSAP_OC_SUM_STARTED_OUTUser-defined 
MSC_Destination_IdMSC_Destination.idUser-defined 
MSC_IdMSC_Destination.Nokia.GSM.INAP_Incoming_Op_Code_Part1.INAP_IOC1_SUM_FAILEDUser-defined 

Nokia NSS MSC Control Unit Report

Report for MSC Control Unit call data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Control_Unit
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Calls (Table)
1)MSC IdMSC.idUser-defined 
10)Subscriber errorsMSC.Nokia.GSM.Control_Unit.cntl_sfailUser-defined 
Trunk circuit errorsMSC.Nokia.GSM.Control_Unit.cntl_efailUser-defined 
2)MSC NameMSC.nameUser-defined 
3)Control Unit IdControl_Unit.idUser-defined 
4)Control Unit NameControl_Unit.nameUser-defined 
5)NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
6)Region IdMSC.RegionUser-defined 
7)AttemptsMSC.Nokia.GSM.Control_Unit.cntl_callsUser-defined 
8)SuccessesMSC.Nokia.GSM.Control_Unit.cntl_accepUser-defined 
9)FailuresMSC.Nokia.GSM.Control_Unit.unsuccessful_callsUser-defined 
Component 2: Successful calls (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Control_Unit.%_successful_calls (Bar)User-defined 
AttemptsMSC.Nokia.GSM.Control_Unit.cntl_calls (Line)User-defined 
SuccessfulMSC.Nokia.GSM.Control_Unit.cntl_accep (Line)User-defined 
Component 3: Unsuccessful calls (Mixed Line/Bar Chart)
% UnsuccessfulMSC.Nokia.GSM.Control_Unit.%_unsuccessful_calls (Bar)User-defined 
AttemptsMSC.Nokia.GSM.Control_Unit.cntl_calls (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Control_Unit.unsuccessful_calls (Line)User-defined 

Nokia NSS MSC Intra GSM Handover Report

Report for MSC Intra-GSM handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.Intra_GSM_Handovers.dropped_callsUser-defined 
IAMSCIAGSMCLEARMSC.Nokia.GSM.Intra_GSM_Handovers.iamsciagsmclearUser-defined 
IEPLMNIAMSCIAGSMCLEARMSC.Nokia.GSM.Intra_GSM_Handovers.ieplmniamsciagsmclearUser-defined 
INIEMSCIAGSMCLEARMSC.Nokia.GSM.Intra_GSM_Handovers.iniemsciagsmclearUser-defined 
INIEPLMNIAGSMCLEARMSC.Nokia.GSM.Intra_GSM_Handovers.inieplmniagsmclearUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
OUTIEMSCIAGSMCLEARMSC.Nokia.GSM.Intra_GSM_Handovers.outiemsciagsmclearUser-defined 
OUTIEPLMNIAGSMCLEARMSC.Nokia.GSM.Intra_GSM_Handovers.outieplmniagsmclearUser-defined 
Region IdMSC.RegionUser-defined 
Component 2: Inter MSC (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_succ_inc_e_msc_i_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_unsucc_inc_e_msc_i_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.succ_inc_e_msc_i_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.unsucc_inc_e_msc_i_gsm_ho (Line)User-defined 
Component 3: Inter MSC (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_succ_out_e_msc_i_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_unsucc_out_e_msc_i_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.succ_out_e_msc_i_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.unsucc_out_e_msc_i_gsm_ho (Line)User-defined 
Component 4: Inter PLMN (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_succ_inc_e_plmn_i_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_unsucc_inc_e_plmn_i_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.succ_inc_e_plmn_i_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.unsucc_inc_e_plmn_i_gsm_ho (Line)User-defined 
Component 5: Inter PLMN (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_succ_out_e_plmn_i_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_unsucc_out_e_plmn_i_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.succ_out_e_plmn_i_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.unsucc_out_e_plmn_i_gsm_ho (Line)User-defined 
Component 6: Inter PLMN Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_succ_plmn_msc_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_unsucc_plmn_msc_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.succ_plmn_msc_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.unsucc_plmn_msc_gsm_ho (Line)User-defined 
Component 7: Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_intramscintragsmok (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.%_intramscintragsmnok (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.intramscintragsmok (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_GSM_Handovers.intramscintragsmnok (Line)User-defined 

Nokia NSS MSC Intra UMTS Handover Report

Report of MSC Intra-UMTS Handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.Intra_UMTS_Handovers.dropped_callsUser-defined 
IAMSCIAUMTSCLEARMSC.Nokia.GSM.Intra_UMTS_Handovers.iamsciaumtsclearUser-defined 
IEPLMNIAMSCIAUMTSCLEARMSC.Nokia.GSM.Intra_UMTS_Handovers.ieplmniamsciaumtsclearUser-defined 
INIEMSCIAUMTSCLEARMSC.Nokia.GSM.Intra_UMTS_Handovers.iniemsciaumtsclearUser-defined 
INIEPLMNIAUMTSCLEARMSC.Nokia.GSM.Intra_UMTS_Handovers.inieplmniaumtsclearUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
OUTIEMSCIAUMTSCLEARMSC.Nokia.GSM.Intra_UMTS_Handovers.outiemsciaumtsclearUser-defined 
OUTIEPLMNIAUMTSCLEARMSC.Nokia.GSM.Intra_UMTS_Handovers.outieplmniaumtsclearUser-defined 
Region IdMSC.RegionUser-defined 
Component 2: Inter MSC (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_succ_inc_e_msc_i_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_unsucc_inc_e_msc_i_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.succ_inc_e_msc_i_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.unsucc_inc_e_msc_i_umts_ho (Line)User-defined 
Component 3: Inter MSC (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_succ_out_e_msc_i_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_unsucc_out_e_msc_i_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.succ_out_e_msc_i_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.unsucc_out_e_msc_i_umts_ho (Line)User-defined 
Component 4: Inter PLMN (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_succ_inc_e_plmn_i_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_unsucc_inc_e_plmn_i_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.succ_inc_e_plmn_i_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.unsucc_inc_e_plmn_i_umts_ho (Line)User-defined 
Component 5: Inter PLMN (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_succ_out_e_plmn_i_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_unsucc_out_e_plmn_i_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.succ_out_e_plmn_i_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.unsucc_out_e_plmn_i_umts_ho (Line)User-defined 
Component 6: Inter PLMN Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_succ_plmn_msc_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_unsucc_plmn_msc_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.succ_plmn_msc_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.unsucc_plmn_msc_umts_ho (Line)User-defined 
Component 7: Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_succ_i_msc_i_umts_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.%_unsucc_i_msc_i_umts_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.succ_i_msc_i_umts_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.Intra_UMTS_Handovers.unsucc_i_msc_i_umts_ho (Line)User-defined 

Nokia NSS MSC Number Destination Report

Report for number destination data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Number_Destination
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Answered Calls (Mixed Line/Bar Chart)
% AnsweredMSC.Nokia.GSM.Number_Destination.%_answered_calls (Bar)User-defined 
AnsweredMSC.Nokia.GSM.Number_Destination.ans_calls (Line)User-defined 
Total callsMSC.Nokia.GSM.Number_Destination.nbr_calls (Line)User-defined 
Component 2: Destination Traffic (Line Chart)
TrafficMSC.Nokia.GSM.Number_Destination.avr_traf_erlangUser-defined 

Nokia NSS MSC Trafficability Report

Report of MSC Trafficability data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Calls answered (Mixed Line/Bar Chart)
BidsMSC.Nokia.GSM.Trafficability.tot_calls (Line)User-defined 
Ratio answered callsMSC.Nokia.GSM.Trafficability.ratio_answered (Stack)User-defined 
answered callsMSC.Nokia.GSM.Trafficability.answered (Line)User-defined 
Component 2: Calls not answered (Mixed Line/Bar Chart)
BidsMSC.Nokia.GSM.Trafficability.tot_calls (Line)User-defined 
Ratio unanswered callsMSC.Nokia.GSM.Trafficability.ratio_not_answered (Stack)User-defined 
unanswered callsMSC.Nokia.GSM.Trafficability.not_answered (Line)User-defined 

Nokia NSS MSC UMA Handover Inter MSC 1 Report

Report for MSC UMA handover inter-MSC report data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.UMA_handovers_inter_MSC.dropped_callsUser-defined 
IN INTER MSC GSM TO UMA DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_gsm_to_uma_dropUser-defined 
IN INTER MSC UMA TO GSM DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_uma_to_gsm_dropUser-defined 
IN INTER MSC UMA TO UMTS DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_uma_to_umts_dropUser-defined 
IN INTER MSC UMTS TO UMA DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_umts_to_uma_dropUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
OUT INTER MSC GSM TO UMA DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_gsm_to_uma_dropUser-defined 
OUT INTER MSC UMA TO GSM DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_uma_to_gsm_dropUser-defined 
OUT INTER MSC UMA TO UMTS DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_uma_to_umts_dropUser-defined 
OUT INTER MSC UMTS TO UMA DROPMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_umts_to_uma_dropUser-defined 
Region IdMSC.RegionUser-defined 
Component 2: GSM-UMA (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_gsm_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_gsm_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_gsm_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_gsm_to_uma_fail (Line)User-defined 
Component 3: UMA-GSM (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_uma_to_gsm_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_uma_to_gsm_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_uma_to_gsm_fail (Line)User-defined 
Component 4: UMA-UMTS (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_uma_to_umts_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_uma_to_umts_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_uma_to_umts_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_uma_to_umts_fail (Line)User-defined 
Component 5: UMTS-UMA (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_umts_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_umts_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_umts_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_umts_to_uma_fail (Line)User-defined 

Nokia NSS MSC UMA Handover Inter MSC 2 Report

Report for MSC UMA handover inter-MSC report data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingNo
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: GSM-UMA (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_gsm_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_gsm_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_gsm_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_gsm_to_uma_fail (Line)User-defined 
Component 2: UMA-GSM (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_uma_to_gsm_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_uma_to_gsm_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_uma_to_gsm_fail (Line)User-defined 
Component 3: UMA-UMTS (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_uma_to_umts_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_in_inter_msc_uma_to_umts_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_uma_to_umts_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.in_inter_msc_uma_to_umts_fail (Line)User-defined 
Component 4: UMTS-UMA (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_umts_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.%_out_inter_msc_umts_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_umts_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_MSC.out_inter_msc_umts_to_uma_fail (Line)User-defined 

Nokia NSS MSC UMA Handovers Intra MSC Report

Report for MSC UMA Handover intra-MSC data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.UMA_handovers_intra_MSC.dropped_callsUser-defined 
INTRA MSC GSM TO UMA DROPMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_gsm_to_uma_dropUser-defined 
INTRA MSC UMA TO GSM DROPMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_uma_to_gsm_dropUser-defined 
INTRA MSC UMA TO UMTS DROPMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_uma_to_umts_dropUser-defined 
INTRA MSC UMTS TO UMA DROPMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_umts_to_uma_dropUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
Region IdMSC.RegionUser-defined 
Component 2: GSM-UMA (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_gsm_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_gsm_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_gsm_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_gsm_to_uma_fail (Line)User-defined 
Component 3: UMA-GSM (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_uma_to_gsm_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_uma_to_gsm_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_uma_to_gsm_fail (Line)User-defined 
Component 4: UMA-UMTS (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_uma_to_umts_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_uma_to_umts_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_uma_to_umts_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_uma_to_umts_fail (Line)User-defined 
Component 5: UMTS-UMA (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_umts_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.%_intra_msc_umts_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_umts_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_intra_MSC.intra_msc_umts_to_uma_fail (Line)User-defined 

Nokia NSS MSC UMA HO Outgoing Inter PLMN

Report for MSC UMA handover outgoing inter-plmn data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.dropped_callsUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
OUT INTER P GSM TO UMA DROPMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_gsm_to_uma_dropUser-defined 
OUT INTER P UMA TO GSM DROPMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_uma_to_gsm_dropUser-defined 
OUT INTER P UMA TO UMTS DROPMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_uma_to_umts_dropUser-defined 
OUT INTER P UMTS TO UMA DROPMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_umts_to_uma_dropUser-defined 
Region IdMSC.RegionUser-defined 
Component 2: GSM-UMA (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_gsm_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_gsm_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_gsm_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_gsm_to_uma_fail (Line)User-defined 
Component 3: UMA-GSM (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_uma_to_gsm_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_uma_to_gsm_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_uma_to_gsm_fail (Line)User-defined 
Component 4: UMA-UMTS (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_uma_to_umts_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_uma_to_umts_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_uma_to_umts_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_uma_to_umts_fail (Line)User-defined 
Component 5: UMTS-UMA (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_umts_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.%_out_inter_p_umts_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_umts_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_outgoing_inter_PLMN.out_inter_p_umts_to_uma_fail (Line)User-defined 

Nokia NSS MSC UMA Incoming Inter PLMN HO

Report for MSC UMA incoming inter plmn handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.dropped_callsUser-defined 
IN INTER P GSM TO UMA DROPMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_gsm_to_uma_dropUser-defined 
IN INTER P UMA TO GSM DROPMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_uma_to_gsm_dropUser-defined 
IN INTER P UMA TO UMTS DROPMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_uma_to_umts_dropUser-defined 
IN INTER P UMTS TO UMA DROPMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_umts_to_uma_dropUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
Region IdMSC.RegionUser-defined 
Component 2: GSM-UMA (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_gsm_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_gsm_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_gsm_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_gsm_to_uma_fail (Line)User-defined 
Component 3: UMA-GSM (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_uma_to_gsm_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_uma_to_gsm_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_uma_to_gsm_fail (Line)User-defined 
Component 4: UMA-UMTS (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_uma_to_umts_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_uma_to_umts_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_uma_to_umts_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_uma_to_umts_fail (Line)User-defined 
Component 5: UMTS-UMA (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_umts_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.%_in_inter_p_umts_to_uma_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_umts_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_incoming_inter_PLMN.in_inter_p_umts_to_uma_fail (Line)User-defined 

Nokia NSS MSC UMTS GSM Handover Report

Report for MSC UMTS GSM handover data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.UMTS_GSM_Handovers.dropped_callsUser-defined 
IEPLMNIAMSCUMTSTOGSMCLEARMSC.Nokia.GSM.UMTS_GSM_Handovers.ieplmniamscumtstogsmclearUser-defined 
INIEMSCUMTSTOGSMCLEARMSC.Nokia.GSM.UMTS_GSM_Handovers.iniemscumtstogsmclearUser-defined 
INIEPLMNUMTSTOGSMCLEARMSC.Nokia.GSM.UMTS_GSM_Handovers.inieplmnumtstogsmclearUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
OUTIEMSCUMTSTOGSMCLEARMSC.Nokia.GSM.UMTS_GSM_Handovers.outiemscumtstogsmclearUser-defined 
OUTIEPLMNUMTSTOGSMCLEARMSC.Nokia.GSM.UMTS_GSM_Handovers.outieplmnumtstogsmclearUser-defined 
Region IdMSC.RegionUser-defined 
Component 2: Inter MSC (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_succ_inc_e_msc_umts_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_unsucc_inc_e_msc_umts_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.succ_inc_e_msc_umts_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.unsucc_inc_e_msc_umts_gsm_ho (Line)User-defined 
Component 3: Inter MSC (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_succ_out_e_msc_umts_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_unsucc_out_e_msc_umts_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.succ_out_e_msc_umts_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.unsucc_out_e_msc_umts_gsm_ho (Line)User-defined 
Component 4: Inter PLMN (incoming) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_succ_inc_e_plmn_umts_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_unsucc_inc_e_plmn_umts_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.succ_inc_e_plmn_umts_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.unsucc_out_e_plmn_umts_gsm_ho (Line)User-defined 
Component 5: Inter PLMN (outgoing) (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_succ_out_e_plmn_umts_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_unsucc_out_e_plmn_umts_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.succ_out_e_plmn_umts_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.unsucc_out_e_plmn_umts_gsm_ho (Line)User-defined 
Component 6: Inter PLMN Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_succ_plmn_msc_umts_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_unsucc_plmn_msc_umts_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.succ_plmn_msc_umts_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.unsucc_plmn_msc_umts_gsm_ho (Line)User-defined 
Component 7: Intra MSC (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_succ_i_msc_umts_gsm_ho (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.%_unsucc_i_msc_umts_gsm_ho (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.succ_i_msc_umts_gsm_ho (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMTS_GSM_Handovers.unsucc_i_msc_umts_gsm_ho (Line)User-defined 

Nokia NSS Processor CDS Load Report

Report for Processor CDS Load data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Processor
Primary ObjectProcessor
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionProcessor
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_CDS_Traffic_Busy_Hour, Nokia_Processor_CDS_Load_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: CDS Load (Line Chart)
LoadProcessor.Nokia.GSM.CDS_CPU_Load.comp_average_loadUser-defined 
Component 2: CDS Message Bus Load (Line Chart)
LoadProcessor.Nokia.GSM.CDS_Message_Bus_Load.mb_load_averageUser-defined 

Nokia NSS Processor HLR Load Report

Report for Processor HLR Load data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Processor
Primary ObjectProcessor
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionProcessor
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_Processor_HLR_Load_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: HLR Message Bus Load (Line Chart)
LoadProcessor.Nokia.GSM.HLR_Message_Bus_Load.loadUser-defined 
Component 2: HLR load (Line Chart)
LoadProcessor.Nokia.GSM.HLR_CPU_Load.loadUser-defined 

Nokia NSS Processor MSC Load Report

Report for Processor MSC Load data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Processor
Primary ObjectProcessor
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionProcessor
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Nokia_Processor_MSC_Load_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Load (Line Chart)
LoadProcessor.Nokia.GSM.MSC_CPU_Load.loadUser-defined 

Nokia NSS Processor MSC Message Bus Load Report

Report for Processor MSC Message Bus Load

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Processor
Primary ObjectProcessor
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionProcessor
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_MSC_Traffic_Busy_Hour, Nokia_Processor_MSC_Load_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Message Bus Load (Line Chart)
LoadProcessor.Nokia.GSM.MSC_Message_Bus_Load.loadUser-defined 

Nokia NSS Processor SRR Load Report

Report for Processor SRR Load data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Processor
Primary ObjectProcessor
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionProcessor
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_SRR_Open_Transaction_Busy_Hour, Nokia_Processor_SRR_Load_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SRR Load (Line Chart)
LoadProcessor.Nokia.GSM.SRR_CPU_Load.compl_load_percent_x10User-defined 
Component 2: SRR Message Bus Load (Line Chart)
LoadProcessor.Nokia.GSM.SRR_Message_Bus_Load.mbload_load_x10User-defined 

Nokia NSS RNC Call Setup Service Report

Report for RNC call setup service data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.RNC
Primary ObjectRNC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRNC
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Calls (Mixed Line/Bar Chart)
% SuccessfulRNC.Nokia.GSM.Call_setup_service.%_successful_calls (Stack)User-defined 
% UnsuccessfulRNC.Nokia.GSM.Call_setup_service.%_unsuccessful_calls (Stack)User-defined 
SuccessfulRNC.Nokia.GSM.Call_setup_service.cssmt_rnc_succ_bids (Line)User-defined 
UnsuccessfulRNC.Nokia.GSM.Call_setup_service.cssmt_rnc_failed_bids (Line)User-defined 

Nokia NSS Route Calls Report

Report for Route_IF Calls Setup data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Route_IF
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Calls Accepted (Mixed Line/Bar Chart)
% AcceptedRoute_IF.Nokia.GSM.Traffic.%_route_accep (Bar)User-defined 
AcceptedRoute_IF.Nokia.GSM.Traffic.route_accep (Line)User-defined 
AttemptsRoute_IF.Nokia.GSM.Traffic.route_attempt (Line)User-defined 

Nokia NSS Route CDS Circuit Group Report

Report for route CDS circuit group data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Route_IF
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_Route_IF_Incoming_CDS_Busy_Hour, Nokia_Route_IF_Outgoing_CDS_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Congestion (Line Chart)
CongestionRoute_IF.Nokia.GSM.CDS_Circuit_Group.cgrcgroup_call_cong_x_100User-defined 
Component 2: Traffic (Line Chart)
Traffic incomingRoute_IF.Nokia.GSM.CDS_Circuit_Group.cgrcgroup_erlangs_in_x_100User-defined 
Traffic outgoingRoute_IF.Nokia.GSM.CDS_Circuit_Group.cgrcgroup_erlangs_out_x_100User-defined 

Nokia NSS Route MSC Circuit Group Report

Report for Route_IF MSC circuit group data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Route_IF
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Congestion (Line Chart)
CongestionRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_call_cong_x_100User-defined 
Component 2: Traffic (Line Chart)
Traffic incomingRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_erlangs_in_x_100User-defined 
Traffic outgoingRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_erlangs_out_x_100User-defined 

Nokia NSS Route Priority Call Report

Report for Route_If priority calls.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Route_IF
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_Route_IF_Bothway_MSC_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Calls (Mixed Line/Bar Chart)
% SuccessfulRoute_IF.Nokia.GSM.Priority_calls.%_nsep_calls (Stack)User-defined 
AttemptsRoute_IF.Nokia.GSM.Priority_calls.nsep_attempts (Line)User-defined 
SuccessfulRoute_IF.Nokia.GSM.Priority_calls.nsep_calls (Line)User-defined 

Nokia NSS Route Traffic Report

Report for Route_IF traffic data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Route_IF
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_Route_IF_Bothway_MSC_Busy_Hour, Nokia_Route_IF_Incoming_MSC_Busy_Hour, Nokia_Route_IF_Outgoing_MSC_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Traffic Bothway (Line Chart)
Bothway trafficRoute_IF.Nokia.GSM.MSC_Circuit_Group.cgrcgroup_accepted_bothwayUser-defined 

Nokia NSS Signalling Link Report

Report for Signalling link data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.Signalling_Link
Primary ObjectSignalling_Link
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_Link
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSUs (Line Chart)
ReceivedSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2.msus_receivedUser-defined 
TransmittedSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2.msus_transmittedUser-defined 
Component 2: Octets (SIF SIO) (Line Chart)
ReceivedSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2.sif_and_sio_octets_receivedUser-defined 
TransmittedSignalling_Link.Nokia.GSM.MSC_Signalling_Point_Util_2.sif_and_sio_octets_transmittedUser-defined 

Nokia NSS UMA HO Inter PLMN Intra MSC Report

Report for UMA handover inter-plmn intra-msc data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Dropped calls (Table)
Dropped callsMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.dropped_callsUser-defined 
INTRP INTRAMSC GSM TO UMA DROPMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_gsm_to_uma_dropUser-defined 
INTRP INTRAMSC UMA TO GSM DROPMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_uma_to_gsm_dropUser-defined 
INTRP INTRAMSC UMA TO UMTS DRPMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_uma_to_umts_drpUser-defined 
INTRP INTRAMSC UMTS TO UMA DRPMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_umts_to_uma_drpUser-defined 
MSC IdMSC.idUser-defined 
MSC NameMSC.nameUser-defined 
NkmtbhNokia_MSC_Traffic_Busy_HourNokia_MSC_Traffic_Busy_Hour 
Region IdMSC.RegionUser-defined 
Component 2: GSM-UMA (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_gsm_to_uma_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_gsm_to_uma_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_gsm_to_uma_fail (Line)User-defined 
Component 3: UMA-GSM (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_uma_to_gsm_succ (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_uma_to_gsm_fail (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_uma_to_gsm_succ (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_uma_to_gsm_fail (Line)User-defined 
Component 4: UMA-UMTS (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_uma_to_umts_suc (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_uma_to_umts_fai (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_uma_to_umts_suc (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_uma_to_umts_fai (Line)User-defined 
Component 5: UMTS-UMA (Mixed Line/Bar Chart)
% SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_umts_to_uma_suc (Stack)User-defined 
% UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.%_intrp_intramsc_umts_to_uma_fai (Stack)User-defined 
SuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_umts_to_uma_suc (Line)User-defined 
UnsuccessfulMSC.Nokia.GSM.UMA_handovers_inter_PLMN_intra_MSC.intrp_intramsc_umts_to_uma_fai (Line)User-defined 

Nokia NSS VLR HLR Subscriber Report

Report for VLR HLR Subscriber data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR, Number_Destination
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_VLR_Subscribers_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Subscribers (Line Chart)
Average subscribersVLR.Nokia.GSM.HLR_Subscribers.ave_subsc_home_hlrUser-defined 

Nokia NSS VLR Location Update Report

Report for VLr Location Update data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_VLR_Subscribers_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Location Updates (Mixed Line/Bar Chart)
AttemptsVLR.Nokia.GSM.VLR_Location_Updates.total_lu_attempts (Line)User-defined 
SuccessfulVLR.Nokia.GSM.VLR_Location_Updates.total_lu_successes (Line)User-defined 
Total LUVLR.Nokia.GSM.VLR_Location_Updates.%_successful_lu (Stack)User-defined 
Component 2: Location Updates GSM (Mixed Line/Bar Chart)
AttemptsVLR.Nokia.GSM.VLR_Location_Updates.total_lu_attempts_gsm (Line)User-defined 
SuccessfulVLR.Nokia.GSM.VLR_Location_Updates.total_lu_successes_gsm (Line)User-defined 
Total LUVLR.Nokia.GSM.VLR_Location_Updates.%_successful_lu_gsm (Stack)User-defined 
Component 3: Location Updates UMTS (Mixed Line/Bar Chart)
AttemptsVLR.Nokia.GSM.VLR_Location_Updates.total_lu_attempts_umts (Line)User-defined 
SuccessfulVLR.Nokia.GSM.VLR_Location_Updates.total_lu_successes_umts (Line)User-defined 
Total LUVLR.Nokia.GSM.VLR_Location_Updates.%_successful_lu_umts (Stack)User-defined 

Nokia NSS VLR Paging Report

Report for VLR paging data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Paging (Mixed Line/Bar Chart)
% SuccessfulVLR.Nokia.GSM.VLR_Paging.%_successful_pagings (Bar)User-defined 
AttemptsVLR.Nokia.GSM.VLR_Paging.total_paging_attempts (Line)User-defined 
SuccessfulVLR.Nokia.GSM.VLR_Paging.total_paging_successes (Line)User-defined 

Nokia NSS VLR SGSN Paging Report

Report for VLR SGSN paging data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionNokia_VLR_Subscribers_Busy_Hour, Average, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Attach Events (Mixed Line/Bar Chart)
% SuccessfulVLR.Nokia.GSM.VLR_SGSN.%_gprs_init_imsi_attach_succ (Bar)User-defined 
AttemptsVLR.Nokia.GSM.VLR_SGSN.gprs_init_imsi_attach_attempt (Line)User-defined 
SuccessfulVLR.Nokia.GSM.VLR_SGSN.gprs_init_imsi_attach_succ (Line)User-defined 
Component 2: Paging (Mixed Line/Bar Chart)
% SuccessfulVLR.Nokia.GSM.VLR_SGSN.%_successful_sgsn_paging (Bar)User-defined 
AttemptsVLR.Nokia.GSM.VLR_SGSN.attempt_sgsn (Line)User-defined 
SuccessfulVLR.Nokia.GSM.VLR_SGSN.succ_sgsn (Line)User-defined 

Nokia NSS VLR Subscribers Report

Report for VLR subscriber data.

Overview

Report FeatureDetails
Report Tree BranchSystem.GSM.Engineering.NSS.Nokia.VLR
Primary ObjectVLR
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionVLR
Date RangingYes
Period SelectionRaw, Daily (Raw), Daily, Weekly, Monthly
Summary SelectionAverage, Maximum, Minimum, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Subscribers (Line Chart)
Average subscribersVLR.Nokia.GSM.Subscribers.tot_ave_subscUser-defined 
Current subscribersVLR.Nokia.GSM.Subscribers.tot_curr_subscUser-defined 


11. Data Availability

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

Grouping ObjectKPI TypeReporting ObjectDefining KPI Group
HLRHLR MobilityHLRHLR.Nokia.GSM.Mobility
MGWMGW IP ATM TrafficMGWMGW.Nokia.GSM.IP_ATM_traffic
MSCMSC HandoverBSCBSC.Nokia.GSM.Handover
MSCMSC TrafficabilityMSCMSC.Nokia.GSM.Trafficability