DEPARTMENT OF TELECOMMUNICATIONS SWITCHING ENGINEERING INSTRUCTIONS [ISSUE No.

1, DATED: 03-02-1999]

ELECTRONIC OCB-283 AT-017

CHECK OF CHARGING MANAGEMENT IN OCB-283 EXCHANGE

1.0 SCOPE This Engineering Instructions describes the procedure of testing the charging management in OCB-283 exchange. 2.0 GENERAL The purpose of testing of charging management is to check the correct functioning of various elements linked to charging of the calls. The elements linked to the charging are the following:
i. ii. iii. iv. v. vi. vii.

viii.
ix.

i. Charging level parameters. ii. Charging calendar. iii. Charging codes. iv. Routine backup of charge accounts. v. Operator backup of charge accounts. vi. Charge account recopying. vii. Excess of charge units per call warning message. Long duration call warning message. ix. Routine observation of charge meters.

3.0

PROCEDURE The testing of the charging management requires two telephones with OAB observation initialized on the test subscriber used as the caller by @OABLA command. The PSAD, PTAX, OPTR, DGNC logical output files are assigned to the operator console by @TDASS command. All parameters available in PTXIN and CTXIN commands should be verified with the REDA. Before doing so it may be censured that the REDA supplied is updated one and it contains all latest information issued by DOT from time to time.

3.1

Check of Management of Charging Level Parameters The purpose of this test to check the correct functioning the different charging parameters used for analysis management. The charging level parameters can be checked for various PTXs available by the following command: @PTXIN:

@ED=YES; The output for a particular PTX (say for PTX=31) will look as below: PTX=31 GFD=0 CTX=31 MCT=0 CPTX=0 MDTX=P 31 TXD=NO For testing of correct functionality of charging parameter we make calls to directions which are having different charging parameters in the existing exchange database or we change the parameters for testing purpose using @PTXMO command. 3.1.1 Check of Charging Method This test is done to check the charging of call either i. ii. iii. By locally generating the charging or By charging on backward received pulses or By charging on received charge band in CCS 7 signalling.

3.1.1.1 Locally Elaborated Charging Method Make calls to the directions whose PTX is having MDTX parameter as MDTX=Pj. At the release of call, check with the results of OAB observation that the calls are charged correctly as defined in MDTX=Pj. These observation are to be repeated for many available CTXs as given in REDA document. 3.1.1.2 Charging on Backward Received Pulses To test charging on backward received pulses we give category as RTT to the incoming trunk group, if loop-back of PCMs is done, if the direct connectivity with TAX exchange is not there. Make calls to the directions whose PTX is having MDTX parameter as MDTX=IM. At the release of call, check with the results of OAB observation that the calls are charged correctly as per the received pulses. 3.1.1.3 Charging by Received Charge Band in CCS 7 Signaling Make calls to the directions whose PTX is having MDTX parameter as MDTX=RTI. At the release of call, check with the results of OAB observation that the calls are charged correctly as per the received charge band from higher exchange. These observations are to be repeated for all defined charge band as given in REDA document. 3.1.2 Check of Subscribers Charge Meter Number This test is to be done to check that the correct subscriber meter number is incrementing, if more than one subscribers meter are used.

Make calls to a direction having PTX parameter CPTX =j. At the release check that correct charge meter of subscriber is incrementing as defined by CPTX=j. This observation is to be repeated for all available values of CPTX as given in REDA. The CPTX value can be changed for a given PTX by PTXMO command. 3.1.3 Check of Detailed Billing Parameter Check for the number of detailed billing groups available from REDA document. Make calls to the directions whose PTX is having GFD parameter as GFD=j (j is the detailed billing group number) from a telephone whose detailed billing category has been assigned (using @ABOMO command with CAT=FDi) corresponding to this GFD as given in REDA document. These observations are to be repeated for all available GFD values as given in REDA document. Save the billing buffer on tape by @FDTIL command. Read this tape using @LECBAN command. Compare the results from the results of OAB observation to check that the correct detailed billing has been prepared for all types of calls. 3.2 Management of Charging Calendar The purpose of this test is to check the correct functioning of the charging calendar for a given day in the year. The charging calendar between two dates can be interrogated by the following command: @CLXIN: @DAT = yy-mm-dd < YY-MM-DD; where, yy-mm-dd earlier date. YY-MM-DD later date. Look for the type of days available in REDA document. Make calls with all the type of the days available by changing the type of the day (current) by the following command. @CLXMO: @DAT=yy-mm-dd, TYP=i, NJO=j; where i= Type of the day j= day number within the week (1<7= Monday < Sunday). Check from OAB observations that the calls are correctly charged as per the types of the day.

To check the day transition message on device assigned PTAX file, change the current time to 23 Hours and 58 Minutes by the following command: @HORMO: @HRS = 23-58-00, DAT=YY-MM-DD; where, YY-MM-DD is the current date. At midnight, check that TYJ, in day transition message is printed out. 3.3 Management of Charging Codes The purpose of this test is to check the correct functioning of various parameters in charging codes. The charging code (CTX) related parameters associated with the PTX can be interrogated using the following command: @CTXIN: @CTX=i, ED=YES; Look for the available values of charging code parameter from the REDA document. The charging code parameter can be changed using the following command: @CTXMO: @TF=i, TYP=j, MTX =---. ---. ---, NTP=k, CTX i; Make calls with all the possible values of parameters of charging code and check from the OAB observations that the calls are correctly charged as per the set parameters.
3.4 3.4

Check of Periodic Safeguard of Subscribers Charge Meters The OCB-283 system has a periodic task TPMCTL which saves automatically the subscribers charge meter to the hard disk in SMM once a day. The purpose of this test to check the good functioning of this backup routine.

3.4.1

Initialization and Check of Activation of Periodic Task TPMCTL Take the start time of the task from the fields IIMSCT (001) and IIMSCT (002) from FBKCN file of O&M with the following command: @ARCHIN: @FICII=BKCN, NOMS=FBKCN2, NUM=0; Verify the status ES of both the TXs using the @ESMIN command.

Check that there are no discrepancies between the files of TXs using @MMCTL command. Take the content of the subscribers charge meters, which is to be used as caller using @TAXIN command. Make a metered call from the callers telephone. Take the new content of the subscribers charge meters, which is to be used as caller using @TAXIN command. Initialize the day and time at 5 minute before the start of the task by the following command. @HORMO: @HRS=HH-MM-SS, DAT= YY-MM-DD Check the start of the safeguard (backup procedure) on the device assigned output file DGNC with the following message: R0501/NCEN=xxx/YY-MM-DD/HH H MM MN SS/CHARGE ACCOUNT BACK-UP Verify the charge meter backup is rejected using Man Machine Command (MMC) during periodic safeguard using the following command; @MMSVX, The output message will be as below: R0501/004/PERIODIC MMSVX RUNNING Check the end of the backup routine on device assigned output file DGNC. R0501/NCEN=xxxx/YY-MM-DD/HH H MM MN SS/END OF CHARGE ACCOUNT BACK-UP Check that the backup routine TPMCTL is written in the calendar for the next day at the same time using the following command: @CALIN: @DAT=YY-MM-DD;
3.4.2 3.4.2

Safeguard Check

Make another metered call from the callers telephone.

Take the new content of the subscribers charge meters of callers telephone using @TAXIN command. Copy FITi file O&M disk to TX2 using the following command: @ARCCO: @MODE=COPY, ARCHS=XATX, FICS=FITxxx, AFD=TX2; where, xxx is the UR number of the caller. Interrogate the content of callers charge meter using the following command; @TAXIN: @NE --.--.--; Check that the backup routine procedure (TPMCTL) has correctly save the subscribers charge meter content to the disk in SMM. The expected output for @TAXIN command will be: DIVERGING METERS TAXTX1=(New incremented meter reading) TAXTX2=(Old meter reading) TAX ARCHIVE=(Old meter reading) 3.5 Saving and Recopying of Subscribers Charge Meters by Man Machine Commands The OCB-283 system has man machine commands command to save the charge accounts to the O&M disk. Only identical accounts in both the charging units (TXs) will be copied to the disk. In case of discrepancies, accounts will be printed out. The backup of the charge accounts on the disk can be done by the following command: @MMSVX; For the diverging charge accounts, it will be printed out from two TXs and O&M as ODIVE faults. To copy the contents of diverging meters from TX1 to TX2, the following command is to be given: @MMTXC: @AFCMD= TX1, NE=xx-yy-zz; CONFORMATION? @YES; After execution of this command check that data in both the TXs are identical by the following command: @MMCTL: @AFCMD - TX, FICH - TAX (x);

3.6 Copying of Subscriber Charge Meter Account and Detail Bill Information on Mag Tape Make some local calls on different charging zones (5 minutes pulse, 3 minutes pulse etc) and some STD calls on different directions and note down the called numbers, time of calls and duration of calls. Assume that observation, SABLA is running on these caller telephones. Now save the charging informations from charging units (TX) to Disks by using the command @MMSVX; Before running this saving command the operator should ensure that there is no discrepancy between charging units, by command @MMCTL. On successful saving of charging meter accounts, copy it. From Disk to Mag tape as per procedure given below. 3.6.1 Copying of Subs Charge Account on Mag Tape And Reading Check that the status of Mag tape drives is ES and available. @INFIL; OPT=BM; Now mount a blank Mag on drive 0 and pre mark it. @BMPMQ: BM=0,VOL=CHARGE, CTRL=NO, UVL=NO; Assign a logical file GTLC to the volume: @BMASS: LFN=GTLC, MNT=YES, VOL=CHARGE, BM=0, IDFIC=SALKIA, CTRL=NO; - Copy the charging account from Disk to tape: @TAXIL: IND=, MIL=. Here IND=Exchange code MIL = Thousand group numbers. - Deassign the volume: @BMASS: LFN=GTLC, VOL =/CHARGE; @BMDMO: VOL=CHARGE; Rewind and Remove the Mag tape from the drive. The protection ring should also be removed. The maintenance personnel should preserve this under safe custody after putting suitable label on it for billing purpose. - Reading the tape:

The A/T personnel can read this tape by using LEC BAN command. The printer should be ON LINE to get hard copy of the subs charge accounts. Mount the tape on the tape drive and set it to load point and ON LINE. Now run the following command. @ LECBAN, CEN=1: TYP=TAX; Check the output of this command for incrementation of meters of the test telephones and compare these with your own records.
3.6.2 3.6.2

Copying of Detail Billing Informations from Disk to Mag Tape

Interrogate the detail billing buffer file on disk. @ FDTIL: OPT=STATUS; Note the number of registered block and filling rate. - Mount a blank mag tape on a drive with write enable ring and set it to load point and ON LINE. - Pre mark the tape with volume name JUSTI 1 @BMPMQ: VOL=JUSTI 1, BM =0, UVL=YES, CTRL=NO; - Assign the volume to the logical file GTDT @BMASS: LFN=GTDT, VOL=JUSTI 1, BM=0, IDFIC=DET BIL, MNT=YES, CTRL=NO; - Copying the details billing information to tape @FDTIL: OPT = SV, NB = xxxxxxxx; Check that archiving of xxx blocks has been taken into account by the system. - Deassign the volume @BMDMO: VOL=JUSTI 1; Rewind and remove the tape from the drive. Remove the write enabled ring and keep it under safe custody for billing purpose. The A/T personnel can read this tape at site as follows. - Mount- the above on a Mag tape drive. - Set it to load point and ON LINE. Set the printer ON LINE. - Assign the volume to logical file UBMF. @BMASS: LFN=UBMF, VOL=JUSTI 1, IDFIC =DET BIL, MNT=YES, BM=0 CTRL=NO; - Tape reading by LEC BAN command. @LEC BAN, CEN =1: TYP=FD, N=x; Where, x is the number of blocks you want to read. Compare the printout with your own record and with the SABLA printout. - Deassign the volume from UBMF and remove it by BMASS and BMDMO commands respectively.
3.7

3.7

Check of Tariff Rate Switchover

Four tier tariff has been introduced in DOT network. The time bands and associated tariff rates are given below for verifications. (a) Ordinary Day Time Bands Tariff Rates 0800 to 1900 hrs. ---- Full rate 0700 to 0800 hrs. ---- 1/2 rate 1900 to 2030 hrs. 0600 to 0700 hrs. ---- 1/3 rate 2030 to 2300 hrs. 2300 to 0600 hrs. ---- 1/4 rate (b) Holiday Time bands Tariff rates 0800 to 2030 hrs.---- 1/2 rate 0000 to 0700 hrs.---- 1/3 rate 2300 to 2300 hrs. 2300 to 0600 hrs. ---- 1/4 rate To check the tariff switch over, change the current time and type of day as per above table by following command. @ HORMO: HRS=HH-MM-SS, DAT=YY-MM-DD @CLXMO: DAT = YY-MM-DD, TYJ=i, NJO=j; Here i=1 or 2 according to ordinary day or holiday and j=1 to 7 number of day. Make some STD calls on different directions and check that meter is incremented as per above table. Similarly cover all the time bands for ordinary day and holiday.
3.8

3.8

Excess of Charge Units Per Call Warning Message

The OCB-283 system has a warning message when the threshold of maximum number of charge unit for one call is exceeded. To interrogate this threshold, the following command is to be given: @ARCIN: @ARCH = XATX, FICH = FIPAX, NOMS=XX0130, NUM=0; The field SEXTCO gives the value of this threshold. Its minimum value is 100. Make a call to a direction (PTX) with fast metering. At the release of the call check results of OAB observations and if the threshold is exceeded, the warning message printed out on PTAX. 3.9 Long Duration of Call Warning Message The OCB-283 system has a warning message when the threshold of maximum duration call is exceeded. Simultaneously, the system can release this call.

To interrogate this threshold, the following command is to be given: @ARCIN: @ARCH = XATX, FICH=FIPAX, NOMS=XX0130, NUM=0; The field DMAXCO gives the value of maximum call duration by step of one hour. According to a TX periodic task, the effective duration is between DMAXCO and DEMAXCO+1 hour. The field RUP is the breaking off mark. If RUP=0, the call will be released when threshold reaches. If RUP=1, the call is not released, but new detailed billing or observation message is eventually initialized and subscribers charge meter is updated. The value for the field DMAXCO in India is set to 1 hour and the value for the field RUP is set to 0. Make a call. At the time out duration check with the results of OAB observations and the warning message printed out on PTAX, according to value of the field RUP. 3.10 OTA Observations

The OCB-283 has a routine, which backup the contents of cumulative total charge observation meters in O&M disk. This pseudo routine OAT is activated when starting up O&M and at 10 a.m., 2 p.m., 6 p.m. and 10 p.m. Check the time of next activation of OAT by the following command: @CALIN: @DAT= yy-mm-dd ; (yy-mm-dd is the current date) Change the current time to 15 minutes before second activationof OAT by the following command : @HORMO: @HRS=HH-MM-SS, DAT = yy-mm-dd; Check the new time of activation of OAT by the following command: @CALIN: @DAT = yy-mm-dd; Interrogate the contents of cumulative total charging observation meters by the following command: @OCIN: @CTO = X1 + XS + XFS i; where, i=FSC name. Wait for message of recording printout on device assigned file OPTR: START OF ARCHIVING FOR CHARGE METERS END OF ARCHIVING FOR CHARGE METERS. Save the OPFA buffer on tape by @ OFAIL command. Read this tape by the @LECBAN command. Compare the results of OTA, OCIN and OAB observations. 3.11 End of Test

At the end of test, come back to correct SEXTCO, DMAXCO and RUP fields in FIPAX file by @ARCMO command. Come back to correct day and time by @HORMO command. Come back to correct charging code by @CTXMO command. Come back to correct day type and number by @CLXMO command. Come back to correct PTX by @PTXMO command. Remove subscribers and circuit group categories by @ ABOMO and @ FSCMO commands. Stop the OAB observation by @OABLA command. 4.0 CONCLUSION The check of charging management is one of the most important test in OCB-283 system. It should be check thoroughly to prevent any type of revenue loss to the department and if any discrepancy is notice, it should be brought to the notice of the installer for necessary corrective action. The maintenance authorities can also be use the relevant portion of this Engineering Instruction whenever any new type of charging is introduced in the network.

Bibliography: Alcatel Acceptance Test Procedure E-10/OCB-R20 Document No. 3-1-3.

END