Technical Report on Value Added Switch OperationsContents1.Introduction22.Charging System22.1 Service Data Point (SDP)22.2 Charging Control Node (CCN)32.3 Account Finder (AF)32.4 Voucher Server (VS)32.5 Mobile IN Service Administration Tool (MINSAT)42.6 Account Information and Refill (AIR)43.Traffic Cases43.1 USSD User Account Refill5Steps53.2 USSD Balance Enquiry6Steps73.3 Originating Charged call7Steps84.Backups105.Daily Routines105.1 SDP105.2 CCN115.3 Voucher Server115.4 MINSAT125.5 AIR126.SMCS137.The Major Role I played in VAS Operations148.Conclusion158.1Way forward15

1. IntroductionThe report gives a brief overview of Charging system and its network elements. Chapter 3 discusses the traffic cases between the network elements while chapter 4 and 5 discusses the backups and daily routines done on each node respectively. The routines carried in each network elements and backups made on the network elements are discussed.

2. Charging SystemCharging system (CS) is a cost efficient charging solution. It helps network operators to charge in real time for events and sessions in the mobile network. The events and sessions can either be voice calls, Short Message Service (SMS) or events using General Packet Radio Service (GPRS). In CS each subscriber is connected to an account that can be refilled. Charging System provides with possibility of market segmentation, tools for tariff management, bonus and loyalty programs. Charging system consists of the following network elements:1) Service Data Point (SDP)2) Charging Control Node (CCN)3) Account Finder (AF)4) Voucher Server (VS)5) Mobile IN Service Administration Tool (MINSAT)6) Account Information and Refill (AIR)

2.1 Service Data Point (SDP)SDP contains the database with subscriber and account information. It performs charging analysis of prepaid calls whereby it does the following tasks; it reserve money from the subscriber account for initiation of a call, administrate the Announcements (e.g. during end of a call there is a tone played, making the calling subscriber to be aware that the call is about to end) and it also update the subscriber account after the call. SDP also assist in refill processes whereby it updates the subscriber account or balance with the money that the voucher worth. SDP helps in processing of Charging Data Records (CDR), it also helps in initiating and sending of Unstructured Supplementary Service Data (USSD) as well as Short Message Services (SMS) notifications. For instance, in USSD balance enquiry SDP communicates with AIR to provide with the balance of the user. SDP administrate or manages the following data:1) Subscribers Account Information 2) Service Classes3) Tariff and Charging Analysis4) Dedicated Accounts5) Subscriber Life Cycle6) USSD and SMS Notification7) Promotion Plan 2.2 Charging Control Node (CCN)CCN is responsible for handling call control in Circuit Switched Networks and Packet Switched Network. CCN plays major roles in the following Traffic cases:1) Originating charging call2) SMS charging3) GPRS real time ChargingCCN provides with session control by communicating with the Account Finder (AF) and Service Data Point (SDP) about the subscriber Account.

2.3 Account Finder (AF)Account Finder provides location information of subscribers accounts. It enables centralized management of multiple SDPs. It stores the IP address of SDPs and it can be used to find the SDP in which the subscriber belongs to. AF is used in the following traffic cases:1) Originating charging call2) Originating charging SMS

2.4 Voucher Server (VS)Voucher server is responsible for administration and storage of vouchers. It is used in USSD account refill whereby it communicates with the AIR. During refill process the AIR send the activation code to the VS so that VS can confirm it as an existing code that has not been used. After successful refill, VS marks the voucher as the used voucher.2.5 Mobile IN Service Administration Tool (MINSAT)MINSAT is the software tool that manages the Charging System service. MINSAT client interface consists of java client that runs on UNIX machines. MINSAT does not handle traffic but it interacts with other systems in real time for provision and updates. The java client has the following areas of management:1) Customer Care: In this case MINSAT is used to handle Subscriber Administration (where the following subscriber information is displayed Subscriber Number, Balance, Supervision Fee Period, Service Fee Period, service Class, HLR profile and barring status), Account History, Account Administration, Service Offering and USSD administration.2) Statistics: In this case MINSAT generates a wide range of financial and statistical reports.3) Operation and Maintenance: MINSAT provides with the capability of checking alarms, configuring alarms and filtering alarms in terms of Alarm Type (software alarm or database alarm), Severity (critical or warning) and State (unacknowledged or acknowledged).

2.6 Account Information and Refill (AIR)AIR is a set of hardware and software that is used for refill functions, refill configurations for promotions and administration of USSD communication. AIR also performs the calculations needed for expiry dates and adding money to the subscriber accounts. The refills that AIR handles are initiated from many different sources both in SS7 network and the IP networks. The AIR system is connected to IVR, SDP, VS, AF and MINSAT systems. AIR is used in the following traffic cases; USSD User Account Refill and USSD Balance Enquiry

3. Traffic CasesTraffic Cases shows the communication between the nodes in Charging System and the responsibility or role of each node.3.1 USSD User Account Refill

Steps

The steps below describes what happens during USSD User Account Refill and the task carried by each node.1) The subscriber sends the USSD message containing the USSD short code used for refill together with the activation code revealed on the Voucher.2) MSC forwards the message to the HLR.3) HLR performs Global Title Translation (GTT) to find the destination of the message using destination Point codes. After GTT, the HLR forwards the message to the correct destination which is AIR.4) Since the location for account information of the subscriber is known by the AF. AIR sends a request to AF to provide with the location of the account information.5) AF provides with the answer to the request whereby it respond with the SDP IP address where the subscriber account resides.6) AIR now interrogates the SDP about the account and the subscriber data information7) SDP replies to AIR and in this point AIR analysis the account and subscriber information. For instance, AIR checks if the subscriber is allowed to make refills and if the subscriber account really exists. It also checks the life cycle dates (Service Fee expiry date, Supervision expiry date and Account Disconnect date). Furthermore, AIR checks the class of service of the subscriber.8) AIR now sends the activation code to the VS for verification. So that VS can determine whether the Voucher has not been used and whether it is an existing Voucher. 9) VS return the answer about the activation code to AIR.10) IF the voucher is valid, then AIR sends a refill request to SDP. The request tells the SDP to update or increase the subscriber balance with the money the voucher worth.11) The account is increased in the SDP database.12) The SDP sends the result of the refill to AIR.13) IF the result shows that the refill was successful, the AIR sends a request to VS to mark the voucher or the activation code as used.14) The VS respond to AIR informing it that it has successfully marked the Voucher as used.15) AIR reformats the respond to the USSD text String and sends it to HLR. IF the response was successful the appropriate message is send to the HLR or a failure message is send explaining the cause of failure if the refill failed.16) HLR passed the response to the MSC so that the response could be played on the user Mobile Station.

3.2 USSD Balance Enquiry

Steps

1) A subscriber initiates a USSD message with the USSD short code that is used for balance enquiry.2) MSC forwards the message to the HLR.3) HLR analysis the USSD short code and performs Global Title Translation (GTT) to find the destination point code where it must forward the message. Then after successful GTT it forwards the message to the AIR.4) AIR interrogates the AF to find the SDP IP address where the subscriber account information resides.5) AF responds to AIR with the SDP IP address.6) AIR asks for the subscribers account information from the SDP.7) SDP send requested account information to the AIR.8) AIR reformats the response from the SDP into USSD text string and sends it to HLR.9) HLR passes the respond to the MSC so that the message could be played on the subscriber Mobile Station.

3.3 Originating Charged call

Steps1) A call is initiated by the subscriber.2) MSC/VLR collects data and forwards the call to CCN.3) CCN ask the AF about the subscriber account location.4) AF responds with the SDP IP address where the subscriber account resides.5) CCN interrogates the SDP about the subscriber account information and CCN analyze the account whereby it checks the barred list and always allowed list (to see which numbers the subscriber is not supposed to call)6) If there is enough money in the subscribers account and the called number is not in the burred list. SDP reserves money for the call from the account and sends the calculated call time to CCN.7) CCN keeps the record of call data received from the SDP and send the reply from SDP to the MSC/VLR to allow the call to take a place.8) When the reserved money from the SDP is about to be finished, MSC/VLR responds to the CCN to ask for more reservation.9) CCN passes the respond to the SDP to make new reservation again.10) SDP updates the account and checks if the balance of the subscribers account is enough to make new reservations. If the balance is enough, the SDP sends the period of new reservation to the CCN.11) CCN passes the respond to the MSC/VLR so that the call can continue. Step 8 to 11 can be repeated as long as the user does not hang up the call bearing in mind that the subscriber still has enough money in his or her account.12) MSC/VLR detects that the reservation period is about to expire or the calculated call time is about to reach the limit, then MSC/VLR request for new reservation from CCN.13) CCN passes the request of new reservation to the SDP.14) SDP updates the account with the money previously reserved and at this point it realize that the balance is not enough to make standard reservation. So, SDP makes the reservation amounting to the balance that remained after update. SDP sends the reservation and the warning tone that warns the subscriber that his or her call might be dropped very soon.15) CCN forwards the message to MSC/VLR.16) AT this point the MSC/VLR detects that the call calculated time is about to reach the limit, hence the MSC/VLR displays the warning tone to the subscriber17) MSC/VLR ends or releases the call, collects data about the released call and sends the information to the CCN.18) CCN acknowledges the call release to the MSC/VLR.19) A final report is send to the SDP by the CCN. It contains the total duration of the call. This is important especially if the call was released by the subscriber before the reservation reaches the limit. 20) In this case the SDP performs the final charging of the call and sends the final report to the CCN.21) If end of call notification is enabled, the SDP sends the SMS information or USSD notification about the information of the call e.g. the time of a call, the subscribers account balance and the cost of the call to the SMSC or HLR.22) SMSC/HLR passes the respond to the MSC/VLR for further delivery to the subscriber.

4. BackupsBackups are part of daily routines which are done daily to store the information that has been handled by the Charging System. The purpose of the backup is to store the files for security reasons and for disaster recovery. The backups are done on the following network elements SDP, VS and AIR. The object below is the backup report.

The commands for backups are run on the UNIX machine using UNIX commands.

5. Daily RoutinesDaily routines are done in order to check the performance of the system and any alarms. The routines are done in two different ways, Using (Graphical User Interface) GUI and Command Line Interface using UNIX commands. The daily routines are done on the following nodes; SDP, MINSAT, AIR and CCN.

5.1 SDPIn SDP the following processes are checked;1) Alarms (on GUI)2) Database status3) SS7 links status4) System load5) The number of subscribers in each SDP6) System backup to tape7) Number of input CDR files8) Log files9) Traffic carried by the SDP

5.2 CCNDaily routines for CCN are done using GUI. The steps carried are shown below.1) Checking alarms on the Alarm Viewer2) Checking backup DBN on the Telorb Manager 3) Checking processor load on the Telorb Manager4) Checking Processor time on the Telorb Manager5) Checking Signaling links on the SS7 Configuration

Daily routines are made successful with the help of CCN management features called Fault management used to check alarms and Configuration Management used to administrate the SS7 links and TelORB Manager. The object below is the report for CCN daily routine.

In the report the severity of alarms is; 1) Critical alarm: this alarm is most important alarm that needs to be attended immediately because it might cause the services to be in a halt state. It is represented by a red color.2) Major alarm: this alarm is also important since it can affect the services to operate in a manner that is not normal. It is represented by a gold color.3) Minor alarm: this alarm is less important since the services can still operate in normal manner but it needs to be cleared in time because it might results in a critical alarm. It is represented by a yellow color.

5.3 Voucher ServerOn the VS, the daily routine is done by checking the following processes on the command line interface:1) Alarms (on GUI)2) The system load 3) Disk space4) Log files5) Traffic on the VS6) Backup on the tape7) Status of the hardware8) Memory left on the system9) Database status10) Processor status

5.4 MINSATOn MINSAT the following processes are checked:1) Alarms2) Database status3) Database backup logs4) System backup logs5) UNIX error logs6) Disk space7) Core files8) Processor load

5.5 AIROn AIR the following process are checked:1) Alarms2) System load3) SS7 links4) System backup to tape5) Disk space6) Log files7) Traffic carried by AIR8) Status of the hardware9) Generation and processing of the CDR

6. SMCS

The report for SMCS is done on the ZTE SMSC. The important measurement calculated from the ZTE SMSC is the Success Rate. Success Rate is defined as the percentage of total number of successful Short Message Services to total number of attempted Short Message Services. ZTE SMSC has 3 store and forward engines which are used to store the Short Message Services before they can be delivered to their destinations. The store engines are SC140, SC141 and SC142. From each store engine the following data is obtained.

1) GSM MO Success: Total number of successful mobile originating SMS.2) GSM MT Success: Total number of successful mobile terminating SMS.3) GSM MO Fail: Total number of mobile originating SMS that were not able to be delivered to the destination.4) GSM MT Timeout FAIL: Total number of mobile terminating SMS that their time expired in the store engine awaiting to be received to their destination.5) GSM MT User Error: Total number of mobile originating SMS that were addressed to wrong destinations that do not exist by the user.6) GSM MT Net Error: Total number of mobile originating SMS that were not received to their destination due to network error.7) GSM MO Success Ratio: Ratio of total number of successful mobile originating SMS to total number of attempted mobile originating SMS.8) GSM MT Success Ratio: Ratio of total number of successful mobile originating SMS to total number of attempted mobile originating SMS.

The report also shows the success rate graph of Success Rate against the number of days in a month. The report is made terms of Mobile Originated SMSs and Mobile Terminating SMSs. The object below shows the SMSC Report.

7. The Major Role I played in VAS OperationsI did the system backups every day and here is the procedure I used:1) Name and label the dates on the backup tapes and insert them in the following nodes (VS01, VS02, SDP3a, SDP3b, SDP4a, SDP4b, SDP5a, SDP5b, AIR01, AIR2, AIR03 and AIR04) after lunch.2) Every morning I would run the backup commands and check if the system has managed to store the information in the backup tapes using secure CRT.3) If the system has successfully backed up the information in the back up tapes, I would then compile the backup report and save it to the VAS backup server.4) If there has not been a successful back up, I would raise the issue to my supervisor and we would do the backups manually and then compile the report.5) When done compiling the report, I would then inject the backup tapes and store them in their storage place and then insert new tapes after lunch.I also played a major role in daily routines and this is the procedure I used;1) I did daily routines on the following nodes VS01, VS02, SDP3a, SDP3b, SDP4a, SDP4b, SDP5a, SDP5b, AIR01, AIR2, AIR03 and AIR04. I used Graphical User Interface and Command Line Interface for checking alarms.2) If there were any alarms on the any of the nodes I would contact my supervisor and work together remove the alarm.3) After checking the alarms and status of the nodes, I would then compile the report and save it to the VAS severs.The other task of each day was the report of ZTE SMSC;1) I used ZTE Anyservice Uniportal to connect to the SMSC and query the GSM measure data. The aim of the report is to take the data for 24 hours and monitor the network performance in terms of SMSs. For instance, to see how much of the attempted SMSs in 24 hours were able to reach their destination.

8. ConclusionThe Training was successfully carried out, though the time was not enough to go thoroughly into Charging System.

8.1 Way forwardThe AIR 01 node has been faulty for a month since I joined the department, I think it is advisable if the fault is solved in time even if it might be a minor fault or alarm because a minor alarm might result into a critical alarm which might then be difficult to be solved. There is no up-to-date network diagram of the actual Charging System architecture. It is also advisable to update the network diagram every time when there has been a change in a network. This would make it easier to trace where the fault has occurred in a network.1

Sheet1

Done by:Lebohang MaphothoaneDate26 April 2011SDP3atar tvf /dev/rmt/0cn

Backup completed at: Tuesday, April 26, 2011 2:49:25 AM CATlmaphoth@hasdp03a>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 15513 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 56 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipSDP3btar tvf /dev/rmt/0cnBackup completed at: Tuesday, April 26, 2011 2:51:21 AM CATlmaphoth@hasdp03b>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 15363 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 56 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipSDP4atar tvf /dev/rmt/0cn

Backup completed at: Tuesday, April 26, 2011 2:49:40 AM CATlmaphoth@hasdp04a>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 15515 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 56 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipSDP4b

Backup completed at: Tuesday, April 26, 2011 3:21:36 AM CATlmaphoth@hasdp04b>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 15361 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 56 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipSDP5aBackup completed at: Tuesday, April 26, 2011 2:58:02 AM CATlmaphoth@hasdp05a>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 15510 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 56 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipSDP5bBackup completed at: Tuesday, April 26, 2011 3:09:40 AM CATlmaphoth@hasdp05b>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 15360 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 56 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipVS01atar tvf /dev/rmt/0cn

back up failed

VS01btar tvf /dev/rmt/0cnBackup completed at: Tuesday, April 26, 2011 3:44:00 AM CATlmaphoth@havsr01b>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 01:30 2011 ./-rw-r--r-- 0/0 13297 Apr 26 01:30 2011 ./SysInfo.txt-rw-r--r-- 0/0 70 Apr 26 01:30 2011 ./Hardware.txt-rw-r--r-- 0/0 31 Apr 26 01:30 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 01:30 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 01:30 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 01:30 2011 ./gzipAIR02tar tvf /dev/rmt/0cnBackup completed at: Tuesday, April 26, 2011 3:34:06 AM CATlmaphoth@haair02>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 11255 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 70 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 31 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzip

AIR03 tar tvf /dev/rmt/0cn Backup completed at: Tuesday, April 26, 2011 2:57:39 AM CATlmaphoth@haair03>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 13131 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 79 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 31 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipAIR04tar tvf /dev/rmt/0cnBackup completed at: Tuesday, April 26, 2011 3:08:51 AM CATlmaphoth@haair04>tar tvf /dev/rmt/0cndrwxr-xr-x 0/0 0 Apr 26 02:00 2011 ./-rw-r--r-- 0/0 10864 Apr 26 02:00 2011 ./SysInfo.txt-rw-r--r-- 0/0 70 Apr 26 02:00 2011 ./Hardware.txt-rw-r--r-- 0/0 31 Apr 26 02:00 2011 ./BackupTOC-r-xr-xr-x 0/0 9641 Apr 26 02:00 2011 ./restore.sh-r-xr-xr-x 0/0 3539 Apr 26 02:00 2011 ./tapetrans.sh-r-xr-xr-x 0/0 63704 Apr 26 02:00 2011 ./gzipAIR01

Backup aborted at: Tuesday, April 26, 2011 2:00:00 AM CATlmaphoth@haair01>tar tvf /dev/rmt/0cntar: /dev/rmt/0cn: I/O error

Sheet2

Sheet3

Sheet1Ericcson CS3.0 CCN Daily Maintenance ReportDateWednesday 27 April 2011Prepared ByLebohang MaphothoaneChecked By#Daily Maintenance ChecklistProcedureComment1Check AlarmsAlarm ViewerCCN01CCN02CCN03see belowsee belowsee below2Backup DBNTelorb ManagerCCN01CCN02CCN03successfulsuccessfulsuccessful3Check Processor LoadTelorb ManagerCCN01CCN02CCN03see belowProc_m0_s19 out of servicesee below4Check Processor TimeTelorb ManagerCCN01CCN02CCN03passedpassedpassed5Check signaling linksSignaling SystemCCN01CCN02CCN03all links upall links upall links upCCN1SeverityTimeTypeObjectTypeInstanceFaultIDCauseMajor20110427 12:05:00 CATProcessingCcnCountersscanKey=Primary-Account-Finder-Error,measureName=CcnPerfCounter,source=_SYSTEM109Threshold crossedMajor20110427 12:10:00 CATProcessingCcnCountersscanKey=Primary-Account-Finder-Error,measureName=CcnPerfCounter,source=Proc_m3_s17109Threshold crossedMajor20110427 12:10:00 CATProcessingCcnCountersscanKey=Primary-Account-Finder-Error,measureName=CcnPerfCounter,source=Proc_m3_s11109Threshold crossedCCN02SeverityTimeTypeObjectTypeInstanceFaultIDCauseCritical20110323 05:48:32 CATEquipmentProcessorProc_m0_s191Processor DisabledMinor20110323 06:33:32 CATEquipmentHW-InventoryGEM1Hardware configuration is changedCCN03SeverityTimeTypeObjectTypeInstanceFaultIDCauseMajor20110427 12:25:00 CATProcessingCcnCountersscanKey=Primary-Account-Finder-Error,measureName=CcnPerfCounter,source=Proc_m3_s21109Threshold crossedMajor20110427 12:25:00 CATProcessingCcnCountersscanKey=Primary-Account-Finder-Error,measureName=CcnPerfCounter,source=_SYSTEM109Threshold crossedMajor20110427 12:25:00 CATProcessingCcnCountersscanKey=Primary-Account-Finder-Error,measureName=CcnPerfCounter,source=Proc_m0_s5109Threshold crossedCCN01CCN02CCN03

Sheet2

Sheet3

April 2011_Success_RateDayDateMTMOTotal AttemptsSuccessful AttemptsFailed AttemptsSuccess RateTotal AttemptsSuccessful AttemptsFailed AttemptsSuccess RateFriday114,996,24810,521,8644,474,38470.16%3,719,5912,270,5981,448,99361.04%Saturday211,691,4018,813,6152,877,78675.39%3,433,2301,996,0541,437,17658.14%Sunday310,269,1037,831,2282,437,87576.26%3,118,1521,812,3221,305,83058.12%Monday412,219,9599,314,3852,905,57476.22%3,788,2812,287,2241,501,05760.38%Tuesday511,855,8959,343,8872,512,00878.81%3,684,9292,279,3031,405,62661.85%Wednesday613,691,7669,886,0733,805,69372.20%3,695,7722,245,1591,450,61360.75%Thursday714,672,23910,709,2913,962,94872.99%3,781,6362,249,4591,532,17759.48%Friday812,211,0219,661,5502,549,47179.12%3,815,6592,289,1971,526,46259.99%Saturday912,161,6199,495,8562,665,76378.08%4,041,2042,297,9881,743,21656.86%Sunday1010,961,1648,701,8832,259,28179.39%3,770,3541,999,2851,771,06953.03%Monday1112,781,94610,304,4072,477,53980.62%4,235,7182,321,6091,914,10954.81%Tuesday1212,829,29010,397,5232,431,76781.05%4,348,2852,420,0711,928,21455.66%Wednesday1312,699,51310,254,3352,445,17880.75%4,254,0232,369,2901,884,73355.70%Thursday1412,739,17410,209,6482,529,52680.14%4,200,9282,304,0801,896,84854.85%

Error_BreakdownDayDateSC 140SC 141SC 142TotalGSM MT Timeout FailGSM MT User ErrorGSM MT Network ErrorTotalGSM MT Timeout FailGSM MT User ErrorGSM MT Network ErrorTotalGSM MT Timeout FailGSM MT User ErrorGSM MT Network ErrorTotalGSM MT Timeout FailGSM MT User ErrorGSM MT Network ErrorTotalFriday128413033654759413512433001302946458341349080393171368459984177406197743199951534124474384Saturday22378338473865087273424083411837097871455345108508348169113359782227530481239162877786Sunday3412699306337467334644857080893206674064063592077042366963771153223281651081782437875Monday451683907640619880211465835123397108752986621097265521381150065164327714641324672905574Tuesday518672374539391763322147722351375797600772519384234993598860958423845191269052512008Wednesday626011031344292911463232391104525405641145328316145956454162151404281536672231376553805693Thursday7346114665648312119531434211454364689411926724311513253612781574962111938053451564843962948Friday8269731409435627752402887246164182376672740895139155705100750496524074161410902549471Saturday97797573084805680614376875278245674799224932999837596271060396247925099271533572665763Sunday10439644942396126849933836405373833267925258584411950332895036140721295981282762259281Monday11498700842507127520525076993104926674908370591115664543976404171023113081645212477539Tuesday1227769224745651738175270689546439057337213209018615769095987186722836541472462431767Wednesday1318469571143801739696161697161425967399182429106235469996556458723034951410962445178Thursday1417972361441447765240173725974397117658582479462095197299842859923957971331302529526

Distribution_By_Node_MTDayDateSC 140SC 141SC 142TotalAttemptsSuccessFailureSRAttemptsSuccessFailureSRAttemptsSuccessFailureSRAttemptsSuccessFailureSRFriday145557513204508135124370.34%4,497,3103148230134908070.00%5,943,1874169126177406170.15%14,996,24810,521,8644,474,38470.16%Saturday23557568268483487273475.47%3,519,926264847187145575.24%4,613,9073480310113359775.43%11,691,4018,813,6152,877,78675.39%Sunday33102772236930873346476.36%3,101,516236087674064076.12%4,064,815310104496377176.29%10,269,1037,831,2282,437,87576.26%Monday43711981283177088021176.29%3,667,621279232387529876.13%4,840,3573690292115006576.24%12,219,9599,314,3852,905,57476.22%Tuesday53610326284700476332278.86%3,562,413280233676007778.66%4,683,156369454798860978.89%11,855,8959,343,8872,512,00878.81%Wednesday641453442999021114632372.35%4,120,2022974874114532872.20%5,426,2203912178151404272.10%13,691,7669,886,0733,805,69372.20%Thursday744542023258888119531473.16%4,404,3233211651119267272.92%5,813,7144238752157496272.91%14,672,23910,709,2913,962,94872.99%Friday83703983292874377524079.07%3,665,772289904576672779.08%4,841,2663833762100750479.19%12,211,0219,661,5502,549,47179.12%Saturday93685429287928680614378.13%3,645,479284625579922478.08%4,830,7113770315106039678.05%12,161,6199,495,8562,665,76378.08%Sunday103322718263772568499379.38%3,288,106260885467925279.34%4,350,340345530489503679.43%10,961,1648,701,8832,259,28179.39%Monday113881351312929975205280.62%3,836,668308758574908380.48%5,063,927408752397640480.72%12,781,94610,304,4072,477,53980.62%Tuesday123885974314779973817581.00%3,859,758312603773372180.99%5,083,558412368795987181.12%12,829,29010,397,5232,431,76781.05%Wednesday133853045311334973969680.80%3,812,695307277773991880.59%5,033,773406820996556480.82%12,699,51310,254,3352,445,17880.75%Thursday143863402309816276524080.19%3,829,052306319476585880.00%5,046,720404829299842880.22%12,739,17410,209,6482,529,52680.14%

Distribution_By_Node_MODayDateSC 140SC 141SC 142TotalAttemptsSuccessFailureSRAttemptsSuccessFailureSRAttemptsSuccessFailureSRAttemptsSuccessFailureSRFriday11,145,48769102845445960.33%1,207,13668823951889757.01%1,366,96889133147563765.20%3,719,5912,270,5981,448,99361.04%Saturday21,041,13960924143189858.52%1,152,53460619554633952.60%1,239,55778061845893962.98%3,433,2301,996,0541,437,17658.14%Sunday3959,69254909041060257.22%1,026,64155153347510853.72%1,131,81971169942012062.88%3,118,1521,812,3221,305,83058.12%Monday41,165,98469791146807359.86%1,262,14469147057067454.79%1,360,15389784346231066.01%3,788,2812,287,2241,501,05760.38%Tuesday51,145,02169708744793460.88%1,184,84368918249566158.17%1,355,06589303446203165.90%3,684,9292,279,3031,405,62661.85%Wednesday61,133,78168333045045160.27%1,223,00667816054484655.45%1,338,98588366945531666.00%3,695,7722,245,1591,450,61360.75%Thursday71,159,69468706247263259.25%1,260,54467726658327853.73%1,361,39888513147626765.02%3,781,6362,249,4591,532,17759.48%Friday81,170,49269437547611759.32%1,259,63569062056901554.83%1,385,53290420248133065.26%3,815,6592,289,1971,526,46259.99%Saturday91,224,52069847252604857.04%1,346,16569141965474651.36%1,470,51990809756242261.75%4,041,2042,297,9881,743,21656.86%Sunday101,137,73660230253543452.94%1,240,78960519763559248.78%1,391,82979178660004356.89%3,770,3541,999,2851,771,06953.03%Monday111,286,69970566758103254.84%1,403,67070196670170450.01%1,545,34991397663137359.14%4,235,7182,321,6091,914,10954.81%Tuesday121,327,96673362459434255.24%1,423,26672770769555951.13%1,597,05395874063831360.03%4,348,2852,420,0711,928,21455.66%Wednesday131,308,52272237258615055.21%1,384,78571162467316151.39%1,560,71693529462542259.93%4,254,0232,369,2901,884,73355.70%Thursday141,311,88270072961115353.41%1,337,92369419864372551.89%1,551,12390915364197058.61%4,200,9282,304,0801,896,84854.85%

MO_GraphDateSuccess Rate (%)DayDateSuccess Rate (%)Friday161.04%Saturday258.14%Sunday358.12%Monday460.38%Tuesday561.85%Wednesday660.75%Thursday759.48%Friday859.99%Saturday956.86%Sunday1053.03%Monday1154.81%Tuesday1255.66%Wednesday1355.70%Thursday1454.85%

MO_Graph

Success Rate (%)DateSuccess RateMO Success Rate For April 2011

MT_Graph DayDateSuccess Rate (%)Friday170.16%Saturday275.39%Sunday376.26%Monday476.22%Tuesday578.81%Wednesday672.20%Thursday772.99%Friday879.12%Saturday978.08%Sunday1079.39%Monday1180.62%Tuesday1281.05%Wednesday1380.75%Thursday1480.14%

MT_Graph

Success Rate (%)DateSuccess RateMT Success Rate For April 2011

140ModuleDategsm mo successgsm mo failgsm mt successgsm mt timeout failgsm mt user errorgsm mt net errorgsm alert scgsm psi successgsm psi failgsm psi timeout failgsm mo totalgsm mt totalgsm mo success ratiogsm mt success ratio1402011-04-0169102845445932045082841303365475943436970001145487455575160.3298.521402011-04-026092414318982684834237833847386502720250001041139355756858.5198.571402011-04-03549090410602236930841269930633746246300000959692310277257.2198.571402011-04-046979114680732831770516839076406192668250001165984371198159.8598.561402011-04-056970874479342847004186723745393912540380001145021361032660.8798.621402011-04-0668333045045129990212601103134429292906000001133781414534460.2798.581402011-04-0768706247263232588883461146656483123546230001159694445420259.2498.521402011-04-086943754761172928743269731409435622766000001170492370398359.3298.521402011-04-096984725260482879286779757308480562912220001224520368542957.0498.331402011-04-106023025354342637725439644942396122761300001137736332271852.9398.51402011-04-117056675810323129299498700842507122999240001286699388135154.8498.381402011-04-127336245943423147799277692247456512879820001327966388597455.2498.561402011-04-137223725861503113349184695711438012838770001308522385304555.298.61402011-04-147007296111533098162179723614414472959240001311882386340253.4198.67

141ModuleDategsm mo successgsm mo failgsm mt successgsm mt timeout failgsm mt user errorgsm mt net errorgsm alert scgsm psi successgsm psi failgsm psi timeout failgsm mo totalgsm mt totalgsm mo success ratiogsm mt success ratio1412011-04-0168823951889731482303001302946458343452750001207136449731057.0198.551412011-04-026061955463392648471240834118370972709890001152534351992652.5998.61412011-04-035515334751082360876485708089320662474030001026641310151653.7298.631412011-04-046914705706742792323465835123397102659230001262144366762154.7898.581412011-04-056891824956612802336147722351375792537370001184843356241358.1698.671412011-04-0667816054484629748742391104525405642912270001223006412020255.4598.641412011-04-0767726658327832116513421145436468943566330001260544440432353.7298.551412011-04-086906205690152899045288724616418232778620001259635366577254.8298.561412011-04-096914196547462846255768752782456742894460001346165364547951.3698.391412011-04-106051976355922608854383640537383322763230001240789328810648.7798.531412011-04-11701966701704308758550769931049266300685000140367038366685098.411412011-04-127277076955593126037270689546439052860310001423266385975851.1298.61412011-04-137116246731613072777161697161425962838150001384785381269551.3898.621412011-04-146941986437253063194173725974397112948950001337923382905251.8898.71

142ModuleDategsm mo successgsm mo failgsm mt successgsm mt timeout failgsm mt user errorgsm mt net errorgsm alert scgsm psi successgsm psi failgsm psi timeout failgsm mo totalgsm mt totalgsm mo success ratiogsm mt success ratio1422011-04-0189133147563741691263931713684599844591920001366968594318765.298.571422011-04-0278061845893934803103451085083481693633340001239557461390762.9798.621422011-04-037116994201203101044635920770423663298320001131819406481562.8898.631422011-04-0489784346231036902926621097265521383554150001360153484035766.0198.581422011-04-058930344620313694547251938423499353387760001355065468315665.998.651422011-04-0688366945531639121783161459564541623912850001338985542622065.9998.621422011-04-0788513147626742387524311513253612784777230001361398581371465.0198.561422011-04-089042024813303833762408951391557053704760001385532484126665.2698.551422011-04-099080975624223770315932999837596273881250001470519483071161.7598.411422011-04-107917866000433455304585844119503323705750001391829435034056.8898.541422011-04-119139766313734087523705911156645434005910001545349506392759.1498.421422011-04-129587406383134123687320901861576903834940001597053508355860.0398.611422011-04-139352946254224068209242910623546993792180001560716503377359.9298.661422011-04-149091536419704048292247946209519723952080001551123504672058.6198.72