Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
SPOTS 
Technical Concept 
Charge@Once V1.1 Technology Plug-In
In addition to the authors named on the cover page the following persons have 
collaborated on this document: 
Pedro Dias ...
Table of Contents 
0 Introduction 
The Charge@Once Technology Plug-In (TP) implements a new feature for SPOTS to 
support ...
Table of Contents 
0.1.1 Object Model 
The following figure shows the containment tree of SPOTS object classes for the 
ch...
Table of Contents 
The following table lists the Managed Object Classes that are supported by 
Charge@Once and their Objec...
Table of Contents 
0.1.2 Metadata - Measurements 
MOC MEAS. TYPE MEAS. Description Reference 
Variable 
NETOPOC INFO Infor...
Table of Contents 
CHARG_CALL Charged calls 
related to voice, 
data/FAX, SMS and 
GPRS 
DATACALL 
DIVER_CALL Diverse Call...
Table of Contents 
0.2 Metadata - Counters 
The following tables show the counters for each new measurement collected by S...
Table of Contents 
(a) PERIOD_KEYWORD “Today” 
“Yesterday” 
"Lastweek" 
“Lastweek” means 
the 7 previous 
complete days 
c...
Table of Contents 
0.4.2 Intelligent Network Service Statistics Report 
Report Name: Intelligent Network Service Statistic...
Table of Contents 
Layout Content: 
Service Statistics Report 
Start Date: <START_DATE> 
End Date: <END_DATE> 
DATE TIME O...
Table of Contents 
0.4.3 Physical Entities in Intelligent Network Analysis Report 
Report Name: Physical Entities Analysis...
Table of Contents 
Measurements: FAIL_ACTIV; SMS_CALL_S; TCAP_PRIM 
Remarks: None 
Layout Content: 
Physical Entities Anal...
Table of Contents 
0.4.4 Incoming Call Attempts Monitoring Cluster Report 
Report Name: Incoming Call Attempts Monitoring ...
Table of Contents 
Layout Content: 
Incoming Call Attempts Monitoring Cluster Report 
Start Date: <START_DATE> 
End Date: ...
Table of Contents 
0.4.5 Incoming peer Network Node Call Attempts Monitoring Report 
Report Name: Incoming peer Network No...
Table of Contents 
Layout Content: 
0.4.6 GPRS Session Analysis Report 
Report Name: GPRS Session Analysis Report 
Report ...
Table of Contents 
Description: This report analysis the GPRS Sessions and monitor the GPRS calls, e.g. 
access to the IP ...
Table of Contents 
Layout Content: 
0.4.7 Prepaid Service Statistics Report 
Report Name: Prepaid Service Statistics Repor...
Table of Contents 
Description: Prepaid service concerns to telecommunications services for which the 
customer have to pa...
Prepaid Service Statistics Report 
Start Date: <START_DATE> 
End Date: <END_DATE> 
Table of Contents 
E 
DAT 
TI 
ME 
E 
O...
Table of Contents 
Layout Content:
Table of Contents 
0.4.8 Prepaid Service: Charged Calls Analysis Report 
Report Name: Prepaid Service: Charged Calls Analy...
Table of Contents 
Layout Content: 
Prepaid Service: Charged Calls Analysis Report 
Start Date: <START_DATE> 
End Date: <E...
Table of Contents 
0.4.9 Prepaid Service: Uncharged Calls Analysis Report 
Report Name: Prepaid Service: Uncharged Calls A...
Table of Contents 
Layout Content: 
Prepaid Service: Uncharged Calls Analysis Report 
Start Date: <START_DATE> 
End Date: ...
Table of Contents 
0.4.10 Prepaid Service: Call Attempts Failure Analysis Report 
Report Name: Prepaid Service Call Attemp...
Table of Contents 
Layout Content: 
Prepaid Service Calls Attempts Failure Analysis Report 
Start Date: <START_DATE> 
End ...
Table of Contents
Upcoming SlideShare
Loading in …5
×

Siemens SPOTS Support for TP-Charge@Once v1.1

265 views

Published on

Siemens SPOTS Support for TP-Charge@Once v1.1

Published in: Mobile
  • Be the first to comment

  • Be the first to like this

Siemens SPOTS Support for TP-Charge@Once v1.1

  1. 1. SPOTS Technical Concept Charge@Once V1.1 Technology Plug-In
  2. 2. In addition to the authors named on the cover page the following persons have collaborated on this document: Pedro Dias SSA COM RD1 NMP SE 0 Introduction..............................................................................................3 0.1 Scope......................................................................................................................3 0.2 Metadata - Counters..............................................................................................8 0.3 Virtual Counters in SPOTS- TP for charge@Once v1.1.....................................8 0.4 Pre-defined reports for Charge@Once V1.1.......................................................8 2/29 .
  3. 3. Table of Contents 0 Introduction The Charge@Once Technology Plug-In (TP) implements a new feature for SPOTS to support the Network Element - Charge@Once. With the introduction of GPRS and UMTS, operators are able to offer new mobile data services and applications to their customers, allowing totally new services and business models creating new revenue streams. Since operators ensure that customers are billed for the services they use, it is essential to answer to the business critical for network operators - optimize billing systems for postpaid customers and real time-capable prepaid systems. The Siemens charge@once is the answer to all rating, tariffing and charging challenges in SS7 and IP networks. It is a modular, highly scalable and flexible system that fulfills the demands for next-generation charging and offers open interfaces, thus enabling smooth integration in the network operator’s existing infrastructure. Charge@once addresses online charging for prepaid subscribers, credit limit supervision for postpaid subscribers and hotbilling for both . 0.1 Scope This document describes the Key Performance Indicators (KPIs), Virtual Counters (VCs) and Predefined Reports (PRs) for the SPOTS TP supporting Charge@Once-1.1 based on the charging Performance Objects (POs) provided by @vantage commander. SPOTS uses the XML Export Interface at the Charge@Once. The XML PM Export Interface is used to offer external management systems access to the POs of the Performance Monitoring application. Within this file type the collector and converter processes are more flexible. The XML files are uploaded every 15 minutes. The data comprised in the files is expected to have a fix granularity of 15 minutes and include just the raw data from the Network Element (NE), i.e. no KPI’s processed in the @Com will be supported by the current TP.
  4. 4. Table of Contents 0.1.1 Object Model The following figure shows the containment tree of SPOTS object classes for the charge@once: NETOPOC IPIFOC SERVLOGICIFOC SS7IFOC CLUSTEROC INSERVOC CLTOC PPSOC SYSRESNEOC NODEOC DESTTYPOC OFFERTYPOC PROCUSEROC DEVCNETCARDOC Figure 1 - Object containment tree for charge@once TP
  5. 5. Table of Contents The following table lists the Managed Object Classes that are supported by Charge@Once and their Object Identifier in SPOTS database. MOC COMMENT NETOPOC One per Network Operator IPIFOC IP Charging Interfaces: Client Interfaces (Payment Online Interface, Radius Interface, Diameter Interface) and Server Interfaces (CORBA Payment Plug-In Interface, GTP’ Interface, Hot Billing Interface, Radius Interface, Diameter Interface) SERVLOGICIFOC Service Logic INSERVOC Intelligent Network Service CLTOC Client Name Object SS7IFOC Signaling System 7 Interface CLUSTEROC Cluster of signaling points NODEOC Incoming peer node defined as a node that routes signaling messages based on their destination point code in the SS7 network PPSOC Prepaid Service DESTTYPOC Destination Type, e.g. Sonatel, special service (can have up to 10 indices) OFFERTYPOC Offer Type, e.g Universal Music UMM (can have up to 10 indices) SYSRESNEOC System resources of the network element PROCUSEROC This object class identifies the process and the user or originator of the process being monitored. It must have five objects associated which identify the TOP 5 processes running on the CPU. Note: This object class results from the concatenation of two POs: “Process Id” and “User Id” DEVCNETCARDOC Device name of the network card for monitor the activity on the network interfaces Figure 2 - Managed Object Classes for charge@once TP
  6. 6. Table of Contents 0.1.2 Metadata - Measurements MOC MEAS. TYPE MEAS. Description Reference Variable NETOPOC INFO Information WRTCK IPIFOC CLIENT Client Interface RCVTRANS CLT_PAYMT Client Interface - Payment Online Interface RCVTRANS CLT_RADIUS Client Interface - Radius Interface RCVTRANS CLT_DIAMT Client Interface - Diameter Interface RCVTRANS SERVER Server Interface RCVTRANS SRV_CRB Server Interface - Corba Payment PlugIn Interface RCVTRANS SRV_GTP Server Interface - GTP’ Interface RCVTRANS SRV_HB Server Interface - Hot Billing Interface RCVTRANS SRV_RADIUS Server Interface - Radius Interface RCVTRANS SRV_DIAMT Server Interface - Diameter Interface RCVTRANS SERVLOGICIFOC SERV_LGC Server Interface - Radius Interface: Service Logic RCVTRANS INSERVOC SERV_STAT Number of Attempts per Service SUCCALL SERV_MANAG Service Management Access Function (SMAF) for GUI Administration Commands ADMINCOM CLTOC CLT_NAME Payment per client name RCVTRANS SS7IFOC FAIL_ACTIV Failed activity tests of the SCP FAILACTIV SMS_CALL_S SMS call attempts SMSCALL TCAP_PRIM Transaction Capabilities Application Part RCVTCAP GPRS_SESS GPRS CREGPRSSESS CLUSTEROC CLUS_CALL Call Attempts SUCCALL NODEOC NODE_CALL Per Node Call Attempts SUCCALL PPSOC PPS Prepaid Services CHARGES PAYMT_CALL Payment Call Attempts PAYMTCALL PLTF_CALL Call Attempts Platform Failures DATAFAIL NET_CALL Call Attempts Network Failures DATAFAIL SUBS_CALL Call Attempts Subscriber Failures DATAFAIL
  7. 7. Table of Contents CHARG_CALL Charged calls related to voice, data/FAX, SMS and GPRS DATACALL DIVER_CALL Diverse Calls NENOUGMONE Y NCONN_CALL Calls not connected related to voice, data/FAX and GPRS NCONNDATACA LL PPS_DUR Durations CONNCALLDUR DESTTYPOC CALL Attempts per Destination Type CALL BC_CALL_D Diverse Calls per Destination Type CALL OFFERTYPOC CALL Call Attempts per Offer Type CALL DATA_CALL Data/Fax Call Attempts per Offer Type DATACALL RMOC_CALL Roaming MOC Call Attempts per Offer Type ROAMINGMOC RMTC_CALL Roaming MTC Call Attempts per Offer Type ROAMINGMTC SMS_CALL_O SMS Call Attempts per Offer Type SMSCALL DATEX_CALL Validity Date Expired Calls per Offer Type CALL NENM_CALL Not Enough Money Calls per Offer Type CALL BC_CALL_O Busy Connection Calls per Offer Type CALL FRCHA_CALL Free of Charge Calls per Offer Type CALL SYSRESNEOC CPU_ACTIV CPU Activity USER MEMY_USAGE Memory Usage PHYMEMY PROCUSEROC CPU_USER TOP 5 CPU Users RSS DEVCNETCARDOC NET_ACTIV Network Activity INPUTPACKET Figure 3 – Classes and measurements
  8. 8. Table of Contents 0.2 Metadata - Counters The following tables show the counters for each new measurement collected by SPOTS TP: lisi141a.pt001.siemens.netPT101169$My DocumentsTP_Charge@Once_1 1_metadata counters.xls 0.3 Virtual Counters in SPOTS- TP for charge@Once v1.1 The detailed Virtual Counter list for the measurements is presented in the following file: lisi141a.pt001.siemens.netPT101169$My DocumentsTP_Charge@Once_1 1_virtual counters.xls 0.4 Pre-defined reports for Charge@Once V1.1 0.4.1 Client and Server Interface Transactions for IP Charging Report Report Name: Client and Server Interface Transactions for IP Charging Report Report Short Name: IFTransIPCharging Target Groups: Network Operation, Network Optimisation Description: Reports the client and server interface transactions for IP charging. This report provides basic indicators like receive transactions, successful transactions, unsuccessful transactions and failure rate for client and server interfaces. The unsuccessful transactions are caused by two main reasons: business reason, e.g. account balance not covered and technical reason, e.g. no connection. Note: The IP Charging is provided by IP Network Elements and Application Servers, which comprises the following scenarios: Policy Router (SSG), an IP Monitor Web/WAP Proxy and the Content Servers (e.g. MMSC, HTTP Content server). Input Parameters: Name Possible Values Remarks
  9. 9. Table of Contents (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (a) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (d) OBJECT IPIFOC Interface Measurements: CLIENT, SERVER Remarks: None Layout Content: Client and Server Interface Transactions for IP Charging Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJ Client Interface Server Interface RcvTrans SuccTrans TransFailRate UnsuccTransBusinessR BusinessTransFailRate UnsuccTransTechnicalR TechnicalTransFailRate RcvTrans SuccTrans TransFailRate UnsuccTransBusinessR BusinessTransFailRate UnsuccTransTechnicalR TechnicalTransFailRate Nr Nr % Nr % Nr % Nr Nr % Nr % Nr % YYYY-MM-DD HH:mm <Interface> CLIENT:RCVTRANS CLIENT:SUCCTRANS VC!cltIFTransFailRate CLIENT:BUSINFAILTRANS VC!cltIFTransFailRateBusinR CLIENT:TECHNFAILTRANS VC!cltIFTransFailRateTechR SERVER:RCVTRANS SERVER:SUCCTRANS VC!srvIFTransFailRate SERVER:BUSINFAILTRANS VC!srvIFTransFailRateBusinR SERVER:TECHNFAILTRANS VC!srvIFTransFailRateTechR
  10. 10. Table of Contents 0.4.2 Intelligent Network Service Statistics Report Report Name: Intelligent Network Service Statistics Report Report Short Name: INServStatistics Target Groups: Network Operation, Network Optimisation Description: This report provides intelligent network (IN) service statistics, such as number of successful inbound and outbound calls, number of error situations leading to an abnormal finishing of the call (caused by the SCF and SSF side), number of PDP context released due to short of money and the call failure rate due to protocol errors or resource problems. NOTE: The Service Control Function (SCF) provides the core functions for the execution of intelligent services since it enables access to the SS7 stack and the related INAP protocols. Basically, the SCF provides the triggering and execution of intelligent services, supports service management, tracing, load control, performance monitoring and ticketing. Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT INSERVOC IN Services Measurements: SERV_STAT Remarks: These IN Service counters are "configurable" within the SLEE in the advantage commander. The configuration of these counters shall be done via administration on site in the SLEE trigger table. In the SLEE trigger table the following services shall be assigned: · Virtual Card Calling (VCC) · Universal Personal Telecommunication (UPT) · Virtual Private Network (VPN) · Number Transaction Service (NTS)
  11. 11. Table of Contents Layout Content: Service Statistics Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJECT SStatSuccCalls SStatFailCalls SStatCallFR SStatShortMsg SStatPDPCont SStatPercPDPCont Nr Nr % Nr Nr % YYYY-MM-DD HH:mm <Service> Number of Successful Calls SERV_STAT:SUCCALL Number of Failure Calls SERV_STAT:FAILCALL VC!inServCallFailRateCall Failure Rate Number of Short Messages SERV_STAT:SHORTMSG SERV_STAT:PDPCONTEXTNumber of PDP Context Due to Short of Money Percentage of PDP Context Release VC!inPercPDPContShortM
  12. 12. Table of Contents 0.4.3 Physical Entities in Intelligent Network Analysis Report Report Name: Physical Entities Analysis in Intelligent Network Report Report Short Name: PhyEntitiesAnalysisIN Target Groups: Network Operation, Network Optimisation Description: This report, analyze physical entities such as Service Switch Point (SSP) and Service Control Point (SCP) in Intelligent Network that implements Service Switch Function (SSF) and Service Control Function (SCF) respectively. It provides basic indicator like number of SMS call attempts and the send and received TCAP primitives. It also provides the number of failure activity tests of the Service Control Point (SCP) that implements the Service Switch Function (SSF). NOTE: Transaction Capability Application Part (TCAP) is an internationally recognized protocol for the handling of non-circuit-related messages. The TCAP protocol provides a means for the reliable transfer of information from one application at a switch location to another application. These "applications" provide IN services such as Home Location Register or Short Message Service. Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT SS7IFOC SS7 Interface
  13. 13. Table of Contents Measurements: FAIL_ACTIV; SMS_CALL_S; TCAP_PRIM Remarks: None Layout Content: Physical Entities Analysis in Intelligent Network Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJECT SCP-FailActTests SMS TCAP SMS-TotalNrIncCAtt TCAP-TotalNrPrimRcv TCAP-TotalNrPrimSent Nr Nr Nr Nr YYYY-MM-DD HH:mm <PhysicalEntity> Number of Failed Activity Tests of SCP FAIL_ACTIV:FAILACTIV Total Number of Incoming SMS Call Attempts SMS_CALL_S:SMSCALL Total Number of TCAP Primitives Received TCAP_PRIM:RCVTCAP Total Number of TCAP Primitives Sent TCAP_PRIM:SENDTCAP
  14. 14. Table of Contents 0.4.4 Incoming Call Attempts Monitoring Cluster Report Report Name: Incoming Call Attempts Monitoring Cluster Report Report Short Name: IncomingCallAttemptClusterMonitor Target Groups: Network Operation, Network Optimisation Description: Report the incoming call attempts that monitor the call attempts related to the cluster of signalling points. The incoming call attempts comprise INAP- (Intelligent Network Application Part) and CAP-(Camel Application Part)- based circuit and packet-switched protocols including SMS. This report include the following indicators: call attempts, incoming calls, successful calls attempts, abnormal terminations TCAP dialogues that comprises all type of SS7-based protocols. The reasons for abnormal terminations are: protocol error, resources problems, overload defense mechanism and load limitation mechanism in relation to all call attempts. Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT CLUSTEROC Cluster Measurements: CLUS_CALL Remarks: None
  15. 15. Table of Contents Layout Content: Incoming Call Attempts Monitoring Cluster Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJECT SS7 Interfaces Call Attempts Failure Call Attempts TotalCAtt SuccCAtt CAttSuccRate FailCAtt CAttFR ProtErrFR OverloadFR LoadLimitationFR Nr Nr % Nr % % % % YYYY-MM-DD HH:mm <Cluster> Total Number of Call Attempts CLUS_CALL:TOTALCALL Number of Successful Call Attempts CLUS_CALL:SUCCALL Call Attempts Successful Rate VC!clustCallAttSuccRate Total Number of Failure Call Attempts CLUS_CALL:FAILCALL Call Attempts Failure Rate VC!clustCallAttFailRate Protocol Errors or Resource Problems CLUS_CALL:ERRCALL Failure Rate Overload Failure Rate CLUS_CALL:OVRFAILCALL Load Limitation Failure Rate CLUS_CALL: LDLIMTFAILCALL
  16. 16. Table of Contents 0.4.5 Incoming peer Network Node Call Attempts Monitoring Report Report Name: Incoming peer Network Node Call Attempts Monitoring Report Report Short Name: IncomingPeerNetNodeCallAttemptMonitor Target Groups: Network Operation, Network Optimisation Description: Report the incoming peer node network call attempts that monitor the call attempts per node. This report include the following indicator: call attempts, successful calls, and unsuccessful calls per peer network node. The type of counted failure category is administrated in the node traffic statistics section. It comprises all types of SS7 protocols and nodes but dedicated failure categories. NOTE: These indicators comprise all SS7 protocols and nodes. Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT NODEOC Node Measurements: NODE_CALL Remarks: None
  17. 17. Table of Contents Layout Content: 0.4.6 GPRS Session Analysis Report Report Name: GPRS Session Analysis Report Report Short Name: GPRSSession Target Groups: Network Operation, Network Optimisation Incoming peer Network Node Call Attempts Monitoring Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJECT Peer Network Node Call Attempts Failure Call Attempts pNode-TotalNrCAtt pNode-SuccCAtt pNode-CAttSuccRate pNode-TotalFailCAtt pNode-CAttFR FailUndefNodeCallpNode-pNode- FRforUndefNode Nr Nr % Nr % Nr % YYYY-MM-DD HH:mm <Node> NODE_CALL:TOTALCALLTotal Number of Call Attempt per peer Node NODE_CALL:SUCCALLSuccessful Call Attempts per peer Node VC!nodeCallSuccRateCall Attempts Success Rate per peer Node NODE_CALL:FAILCALLTotal Number of Failure Call Attempts per peer Node VC!nodeCallFailRateCall Attempts Failure Rate per peer Node Call Attempts Failed Undefined Node Call NODE_CALL:FAILUNDNODECALL VC!nodeCallFailRateUndNodeCall Attempts Failure Rate for Undefined Node Call
  18. 18. Table of Contents Description: This report analysis the GPRS Sessions and monitor the GPRS calls, e.g. access to the IP network. It provides basic indicators like total number of open, started and terminated GPRS sessions. The successful and unsuccessful establishment PDP context. Note: GPRS (General Packet Radio Services) is a packet-based wireless communication service that supports data rates from 56 up to 114 Kbps and continuous connection to the Internet for mobile phone and computer users. GPRS is based on Global System for Mobile (GSM) communication and complements existing services such as circuit-switched cellular phone connections and the Short Message Service (SMS). Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT SS7IFOC SS7 Interface Measurements: GPRS_SESS Remarks: None
  19. 19. Table of Contents Layout Content: 0.4.7 Prepaid Service Statistics Report Report Name: Prepaid Service Statistics Report Report Short Name: ppsStatistics Target Groups: Network Operation, Network Optimisation GPRS Session Analysis Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJECT NrStartGPRSSess NrTermGPRSSess NrOpenGPRSSess NrSuccEstabPDPCon NrEventRepDisconn NrRcvReleaEntities SuccEstabPDPContRate Nr Nr Nr Nr Nr Nr % YYYY-MM-DD HH:mm <SS7Interface> Total Number of Started GPRS Sessions GPRS_SESS:CREGPRSSESS Total Number of Terminated GPRS Sessions GPRS_SESS:TERGPRSSESS Total Number of Open GPRS Sessions GPRS_SESS:CONGPRSSESS Number of Successful GPRS_SESS:ESTGPRSSESSPDP Context Establishments Number of Event Reports Disconnected GPRS_SESS:DISCONNEVENT Number of Received Released Entities GPRS_SESS:RCVGPRSENTY Successful Establishment PDP Context Rate VC!gprsSuccEstabPDPContRate
  20. 20. Table of Contents Description: Prepaid service concerns to telecommunications services for which the customer have to pay in advance. Prepaid Accounts are authenticated and debited in real time to ensure that account balance never cross the zero threshold. This report, give us an overview of prepaid services behavior. It provides basic performance indicators as following: total number of PDP context establishment, total number of charged and uncharged calls, total number of subscribers with expiration data reached and provide mean holding time (MHT) statistics. It also monitors requests and failures of the Online Interface. Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT PPSOC Prepaid Service Measurements: PPS; PPS_DUR; PPS_ONLIF; RMTC_CALL; RMOC_CALL Remarks: None
  21. 21. Prepaid Service Statistics Report Start Date: <START_DATE> End Date: <END_DATE> Table of Contents E DAT TI ME E OBJ CT Mean Holding Time (MHT) Statistics Normal Calls Online IF MHT-RechargeServCall MHT-VoiceCAtt TotalNrChargCalls TotalNrUnchargCall CallAttFR TotalNrSubscExpDateR TotalNrPDPCont NrOnlineIFIncomingReq NrOnlineIFOutgoingReq OnlineIFFR Sec Sec Nr Nr % Nr Nr Nr Nr % YYYY-MM-DD HH:mm <PPS> Mean Recharge Service Call Holding Time VC!meanRechServCallHoldTime Mean Voice Call Attempts Holding Time PPS_DUR:VOICECALLDUR/(RMOC_CALL:ROAMINGMOC+RMTC_CALL:ROAMINGMTC) Total number of charges PPS:CHARGES Total Number of Uncharged Calls (DATEX_CALL:CALL+NENM_CALL:CALL+BC_CALL_O:CALL+FRCHA_CALL:CALL+BC_CALL_D:CALL) aggregated per PPS. Call Attempt Failure Rate VC!ppsCallAttFailRate Total Number of Subscribers with Expiration Date Reached PPS:EXPIRATIONDATE Total Number of PDP Context Established by GPRS PPS:PDPCONTESTAB Number of Online Interface Incoming Requests PPS_ONLIF:INCOMINGREQ Number of Online Interface Outgoing Requests PPS_ONLIF:OUTGOINGREQ Online Interface Failure Rate For Timeout of External System VC!onlineIFFailRate
  22. 22. Table of Contents Layout Content:
  23. 23. Table of Contents 0.4.8 Prepaid Service: Charged Calls Analysis Report Report Name: Prepaid Service: Charged Calls Analysis Report Report Short Name: ppsChargedCallAnalysis Target Groups: Network Operation, Network Optimisation Description: This report comprises statistics related to charged calls, including normal and payment calls per offer and destination type. It presents four types of charged calls: voice, data/fax, SMS and GPRS. Within this report it is possible to identify the number and percentage of each prepaid service charged calls type. Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT PPSOC; OFFERTYPOC; DESTTYPOC. Prepaid Service; Offer Type; Destination Type. Measurements: PPS; CHARG_CALL; PLATF_CALL; NET_CALL; SUBSC_CALL; DATEX_CALL; NENM_CALL; BC_CALL_O; BC_CALL_D Remarks: None
  24. 24. Table of Contents Layout Content: Prepaid Service: Charged Calls Analysis Report Start Date: <START_DATE> End Date: <END_DATE> DATE TIME OBJECT Charged Calls TotalNrChargCalls PercChargCalls Voice Data/Fax SMS GPRS NrChargVoiceCalls PercChargVoiceCalls NrChargDataCalls PercChargDataCalls NrChargSMSCalls PercChargSMSCalls NrChargGPRSCalls PercChargGPRSCalls Nr % Nr % Nr % Nr % Nr % YYYY-MM-DD HH:mm <PPS> Total number of charges PPS:CHARGES Percentage of charged calls 100*(PPS:CHARGES/ (PPS:CHARGES+DATEX_CALL:CALL+ NENM_CALL:CALL+BC_CALL_O:CALL+FRCHA_CALL:CALL+ BC_CALL_D:CALL) ) aggregated per PPS. Number of Charged Voice Calls CHARG_CALL:VOICECALL Percentage of Charged Voice Calls VC!ppsPercChargVoiceCall Number of Charged Data/Fax Calls CHARG_CALL:DATACALL Percentage of Charged Data/Fax VC!ppsPercChargDataCall Number of Charged SMS Calls CHARG_CALL:SMSCALL Percentage of Charged SMS Calls VC!ppsPercChargSMSCall Number of Charged GPRS Calls CHARG_CALL:GPRSCALL Percentage of Charged GPRS Calls VC!ppsPercChargGPRSCall
  25. 25. Table of Contents 0.4.9 Prepaid Service: Uncharged Calls Analysis Report Report Name: Prepaid Service: Uncharged Calls Analysis Report Report Short Name: ppsUnchargedCallAnalysis Target Groups: Network Operation, Network Optimisation Description: This report comprises statistics related to the uncharged call attempts, including diverse calls due to validity date expired, not enough money per offer and destination type. NOTE: These performance indicator are associated to different “call parameters” as the following: · Call Type : voice, SMS, data/fax, GPRS, payment · Destination Type : Sonatel, special service · Offer Type : Universal Music (UMM) Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT PPSOC OFFERTYPOC DESTTYPOC Prepaid Service Offer Type Destination Type Measurements: DIVER_CALL; DATEX_CALL; NENM_CALL; BC_CALL_O; FRCHA_CALL; SUBSC_CALL; DATEX_CALL; NENM_CALL; BC_CALL_D Remarks: None
  26. 26. Table of Contents Layout Content: Prepaid Service: Uncharged Calls Analysis Report Start Date: <START_DATE> End Date: <END_DATE> E DAT TIME OBJECT Uncharged Call Types Call Offer Destination TotalNrUnchargCall PercUnchargCalls UCallNotEnCredit UCAttRechargServ UCConnRechargServ ValidDateExpCalls PercValidDateExpCallsOT NotEnogMoneyCallsOT PercNotEnogMoneyCallsOT BusyConnCallsOT PercBusyConnCallsOT FreeChargeCallsOT PercFreeChargeCallsOT BusyConnCallsDT PercBusyConnCallsDT Nr % Nr Nr Nr Nr % Nr % Nr % Nr % Nr % YYYY-MM-DD HH:mm <PPS> Total Number of Uncharged Calls (DATEX_CALL:CALL+NENM_CALL:CALL+BC_CALL_O:CALL+ FRCHA_CALL:CALL+BC_CALL_D:CALL) aggregated per PPS. Percentage of Uncharged Call100*(TotalNrUnchargCall/ TotalNrUnchargCall+PPS:CHARGES) s Number of GPRS Calls with Not Enough Credit to Establish Call DIVER_CALL:ENOUGMONEY Number of Calls Attempts to Recharging Service DIVER_CALL:RECHSERVCALL DIVER_CALL:RECHSERVCONNNumber of Calls Connected to the Recharging Service Number of Calls with Validity Date Expired per Offer Type DATEX_CALL:CALL Percentage Calls with Validity Date Expired per Offer Type VC!ppsPercCallValidDateExp Number of Calls with Not Enough Money Calls per Offer type NENM_CALL:CALL Percentage of Calls with Not Enough Money Calls per Offer type VC!ppsPercCAllNotEnougMon Number of Calls with Busy Connection per Offer Type BC_CALL_O:CALL Percentage of Calls with Busy Connection per Offer Type VC!ppsPercBusyConnCall Number of Free of Charge Calls per Offer Type FRCHA_CALL:CALL Percentage of Free of Charge Calls per Offer Type VC!ppsPercBusyConnCall Number of Calls with Busy Connection per Destination type BC_CALL_D:CALL Percentage of Calls with Busy Connection per Destination type VC!ppsPercBusyConnCallDest
  27. 27. Table of Contents 0.4.10 Prepaid Service: Call Attempts Failure Analysis Report Report Name: Prepaid Service Call Attempts Failure Analysis Report Report Short Name: ppsCallAttemptFailureAnalysis Target Groups: Network Operation, Network Optimisation Description: This report comprises statistics related to call attempts failures per offer and destination type. Those failures are caused by the following reasons:  Platform failures (internal service process error, internal platform error);  Network-related failures (outgoing trunk overload, SSP not available, etc.);  Subscriber related failures (forbidden number dialed, no more credit, expiration date reached). Input Parameters: Name Possible Values Remarks (a) PERIOD_KEYWORD “Today” “Yesterday” "Lastweek" “Lastweek” means the 7 previous complete days counting from today. (b) START_DATE Any date (c) END_DATE Any date (d) AGGREGATION “DTOT” “TEVL” “SPBH Daily Peaks” (e) OBJECT PPSOC; OFFERTYPOC; DESTTYPOC. Prepaid Service; Offer Type; Destination Type. Measurements: PLATF_CALL; NET_CALL; SUBSC_CALL; PAYMT_CALL Remarks: None
  28. 28. Table of Contents Layout Content: Prepaid Service Calls Attempts Failure Analysis Report Start Date: <START_DATE> End Date: <END_DATE> E DAT TI ME E OBJ CT TotalNrCAtt Failures CallAttFR Platform Network Subscriber TotalNrCAttPlatfFail PPSCAttPlatfFR VoiceCAttPlatfFail DataCAttPlatfFail SMSCAttPlatfFail GPRSCAttPlatfFail TotalNrCAttNetFail PPSCAttNetFR VoiceCAttNetFail DataCAttNetFail SMSCAttNetFail GPRSCAttNetFail TotalNrCAttSubscFail PPSCAttSubscFR VoiceCAttSubscFail DataCAttSubscFail SMSCAttSubscFail GPRSCAttSubscFail Nr % Nr % Nr Nr Nr Nr Nr % Nr Nr Nr Nr Nr % Nr Nr Nr Nr YYYY-MM-DD HH:mm <PPS> Total Number of Call Attempts PAYMT_CALL:PAYMTCALL Call Attempt Failure Rate VC!ppsCallAttFailRate Total number of call attempts resulting with platform failures VC!ppsNrCallAttPlatfFail Prepaid service call attempts platform failure rate VC!ppsCallAttPlatfFailRate Number of Voice call attempts resulting with platform failures PLTF_CALL:VOICEFAIL Number of Data/Fax call attempts resulting with platform failures PLTF_CALL:DATACALL Number of SMS call attempts resulting with platform failures PLTF_CALL:SMSFAIL Number of GPRS call attempts resulting with platform failures PLTF_CALL:GPRSFAIL Total number of call attempts resulting with network-related failures VC!ppsNrCallAttNetFail Prepaid service call attempts network failure rate VC!ppsCallAttNetFailRate Number of Voice call attempts resulting with network-related failures NET_CALL:VOICEFAIL Number of Data/Fax call attempts resulting with network-related failures NET_CALL:DATAFAIL Number of SMS call attempts resulting with network-related failures NET_CALL:SMSFAIL Number of GPRS call attempts resulting with network-related failures NET_CALL:GPRSFAIL Total number of call attempts resulting with subscriber related failures VC!ppsNrCallAttSubscFail Prepaid service call attempts subscriber failure rate VC!ppsCallAttSubscFailRate Number of Voice call attempts resulting with subscriber related failures SUBS_CALL:VOICEFAIL Number of Data/Fax call attempts resulting with subscriber related failures SUBS _CALL:DATAFAIL Number of SMS call attempts resulting with subscriber related failures SUBS _CALL:SMSFAIL Number of GPRS call attempts resulting with subscriber related failures SUBS _CALL:GPRSFAIL
  29. 29. Table of Contents

×