Traffic

31
Traffic Administration

Transcript of Traffic

Page 1: Traffic

Traffic Administration

Page 2: Traffic

Traffic Administration

The OMN:EXCH-TR comprises the functions to be carried out in the exchange within the scope of traffic data recording. Traffic data recording is divided into the following :

1.    Traffic Measurement

2.  Traffic Data Monitoring

3.  Traffic Structure Measurement

4.  Traffic observation

5. Directory Number Observation

Page 3: Traffic

Traffic Administration

1. Traffic Measurement       Measures events and status duration, e.g.,

-Number of successful seizures of CRs in an LTG

-Number of delays during the seizures of code receivers in an LTG

-Number of incoming seizures from subscriber without dial signal etc.

Task:Traffic measurement provides data for the planning and operation of the exchange and the network.

Page 4: Traffic

Traffic Administration

2 Traffic Data Monitoring

      Periodically compares software meter status with predefined threshold value. If the threshold value is exceeded, messages and data will be displayed that may indicate the call-processing problems.

     Task:Traffic overload may be prevented by traffic management measures.

Page 5: Traffic

Traffic Administration

3. Traffic Structure Measurement       Collects the data of individual calls in the form of data records,

or records data concerning traffic flow.

 Task:The purpose of traffic structure measurement is to supply information about the volume, distribution and success of switching operations.

Traffic structure measurement is divided into:-Trunk group traffic structure measurement

-Total traffic structure measurement

-Originating traffic structure measurement

Page 6: Traffic

Traffic Administration4. Traffic observation Records call-related data & utilisation of affected objects.

     Task:The objective of traffic observation is to record and output values and data observed during the processing of statistically selected calls to analyse the following:

- system and network behaviour- system performance- grade of service - quality of service - traffic structure- subscriber or signalling behaviour

Page 7: Traffic

Traffic Administration   5. Directory Number Observation

Records call related data of subs. or PBX lines under obs. by ordinary calls or subs. controlled inputs,e.g.:

- Directory number - Local area code- Types of line

- Seizure time - Call duration

- Traffic type - Service - Subscriber feature

 Task : The objective of directory number observation is to get a closer analysis of

subscriber behavior.

Page 8: Traffic

• The traffic measurement for single objects is The traffic measurement for single objects is activated via traffic measurement orders. activated via traffic measurement orders.

• The measured data is object-related.The measured data is object-related.

• Measurements may be taken on the following Measurements may be taken on the following objects:objects:

Traffic Measurement

Traffic Object Command to initiate the

traffic measurementDestinations REC DEST

Announcement groups REC ANGRP

Private branch exchange REC PBX

Subscriber REC SUB

DLU REC DLU

Page 9: Traffic

Traffic Measurement

Trunk group REC TGRP

LTG REC LTG

Discarded CCS7 message signal units REC C7 DCD MSU

CCS7 destination point traffic data REC C7 DP

CCS7 route set traffic REC C7 RSET

CCS7 signaling link grade of service REC C7 GOS

CCS7 signalling link load REC C7 L LOAD

Co-ordination processor REC CP

Traffic flow REC TRAFLOW

Peak hour ENTR ADPH MEAS

Page 10: Traffic

Traffic MeasurementService application frequency

REC SAF

Exchange grade of service REC EXCH

V5.2 interfaces REC V5IF

Subscriber REC DN

Load on D-channel REC IBADCH

Page 11: Traffic

Procedure for Traffic measurement

 -Call processing programs count the events and measure the status duration in the GP and CP, e.g. no. of seizures in GP.

-The call processing programs transfer the collected data to a buffer (traffic data saving).

-The traffic measurement recording programs read out the buffered data from the traffic data buffer and transmit it to the system disk

File name = TS.<object>.I<increment>

TS.<object>.<weekday><increment>

or edit and transmit the data to the assigned operating equipment

Page 12: Traffic

Procedure for Traffic measurement

-To specify the destination equipment as a disk or operating equipment.

REC <object> : UNIT = MDD/OMT, .... ;

-Traffic data are normally evaluated by means of post processing. The traffic measurement files may be copied onto magnetic tape/ magneto optical disk for this purpose

-The traffic measurement data may be edited and logged on the input device with GET TRAFILE.

-Furthermore, an overview of the traffic measurement files and traffic measurement orders may be displayed.

Page 13: Traffic

To create Groups of Traffic Objects

•Objects to be subject to Traffic Administration can be compiled in Traffic Object groups.

•These groups may be assigned any name.

•The group type is selected in accordance with the objects to be observed.

CR TR O GRP: GRP = <group name>,

GRPTYP = {DEST, PBX, TGRP, etc.}

To add traffic objects in a group so defined,

ENTR TRO PBX : GRP = ,

DN = , LAC = ; or

ENTR TRO DEST: GRP = ,

DOCODE = , [DLAC = ] ;

Page 14: Traffic

To create Groups of Traffic Objects

•Upto 50 groups may thus be formed. An Object Group for destination area may contain upto 512 objects. Similarly an Object Group for PBXs may contain upto 256 PBXs.

   To display the created Object Groups,

  DISP TRO GRP;

    To display all the objects in a specific Object Group,

  DISP TRO : GRP = group name;

Page 15: Traffic

MML commands for traffic Measurement

1. To activate traffic measurement,

REC <object>:

Name of Traffic Object / Traffic Object Group,

UNIT = OMT/ MDD - single/ MDD - daily,

BEG = <yy> - <mm> - <dd>, job begin within a month

TER =<yy> - <mm> - <dd>, job termination within a year

IV = hh1 - mm1 - hh2 - mm2,

PER = SU/MO/ ……. /SA/WO/HO;

• Job is accepted only when the system time is secure. 

• Up to 16 traffic measurement orders may be entered, 8 of which may refer to the same object.

Page 16: Traffic

DISPTRAMORD: STATUS=All; ALTTC/A39336D0032/INDCPVIV6642-775/000/OMT-01/SKJ97-03-03 16:31:31

6076 2893/ 00894 Job No. Rec Command B:Begin Interval Period Filename

Object E:End6068 Cmd :RecCP B:97-03-04 (Unit = OMT)

IntTim = 1805507 Cmd :RecGP B:97-03-03 TS.GPXX.MO 1

LTG = 0-01&&0-065518 Cmd :RecGP B:97-03-03 TS.GPXX.MO 2

LTG = 0-07&&0-095525 Cmd :RecGP B:97-03-04 TS.GPXX. I 01

LTG = 0-07&&0-095939 Cmd :RecSub B:97-03-04 (Unit = OMT)

LAC = 0575 DN =5300000 &

5300026 &5300027

5962 Cmd :RecGP B:97-03-04 (Unit = OMT) LTG = 0-01&&0-05

2. To list running traffic measurement jobs,

Page 17: Traffic

MML commands for traffic Measurement

3. To display the measured Traffic figures

The traffic measurement data may be edited and logged on the input device with GET TRAFILE.

Furthermore, an overview of the traffic measurement file characteristics orders may be displayed by DISP TRAFICH

4. To cancel a Traffic Measurement job

A traffic measurement order is stored in the system as a semipermanent job.

Semipermanent means the jobs are stored on the disk and are restarted automatically after recovery.

A Traffic Measurement Job can be cancelled before the entered termination date by using the command CAN JOB.

Page 18: Traffic

To measure the Exchange Traffic, BHCA, CCR

< GETTRAFILE: FILE = TS.GOSX.SA2, SEL = EXCH, IV = 09-00-23-00;

NOIDA/A39336D0029/INDCPVIV6640-508/010/OMT-01/SDE94-12-12 10:54:57

1591 2893/06159DATE TIME TC(dErl) TOTAL SUCCESSFUL ANSWERED

DATA CALLS CALLS CALLS

QUALITY94-12-10 09.15 2403 3228 2067 1096

Secure94-12-10 09.30 2684 3772 2386 1308

Secure94-12-10 09.45 2731 4251 2660 1342

Secure94-12-10 10.00 2944 4561 2928 1486

Secure94-12-10 10.15 3281 5336 3302 1652

Secure94-12-10 10.30 3350 5022 3387 1626

Secure94-12-10 10.45 3354 4979 3454 1630

Secure94-12-10 11.00 3575 5745 3898 1713

Secure94-12-10 11.15 3513 5763 3910 1698

Secure94-12-10 11.30 3473 5712 3972 1659

Secure94-12-10 11.45 3474 5562 3856 1618

Secure94-12-10 12.00 3485 5607 3865 1579

Secure

Page 19: Traffic

Determining the Busy Hour

-The daily peak hour is the hour of a day when the highest traffic measured on TGRP/PBXs is recorded.

-ADPH Measurement is used to calculate the average values of the daily peak hours during a period of 14 days

-The EWSD determines the traffic load values in the busy hour by the "Average of Daily Peak Full Hour" method (ADPFH).

-The recorded data are output in daily files. Files are created for two weeks.

-The ADPFH measurement records following measured data, among other things:

- the beginning of the hour with the highest traffic intensity

- the traffic intensity (total incoming and outgoing)

- the sliding mean value of the traffic intensity

- the time during which all trunks are busy

- the number of cases when all trunks are busy

Page 20: Traffic

Average Daily Peak Hour Traffic Measurement (ADPHMEAS) jobs

-Up to 200 trunk groups (TGRP) and up to 600 PBXs can be included in the ADPFH measurement.

-New measurement objects can be included in the measurement at any time & measurement objects can be cancelled. For new measurement objects, measurement begins at 0:00 hours on the next measurement day.

-To enter measurement objects in the ADPFH job listENTR ADPHMEAS:

TGNO = <trunk group number>,

GRP = <traffic object group>,

DN = <PBX directory number>,

[LAC = <local area code>] ;

Page 21: Traffic

Average Daily Peak Hour Traffic Measurement (ADPHMEAS) jobs

-To display ADPFH job data

DISP ADPHMEAS:

STATUS = <status> ,

TGNO = <trunk group number>,

GRP = <traffic object group>,

DN = <PBX directory number>,

LAC = <local area index>;

-To activate ADPFH measurement job

ACT ADPHMEAS:

TGNO = <trunk group number>,

GRP = <traffic object group>,

DN = <PBX directory number>,

PER =

Page 22: Traffic

Traffic Data Monitoring

1. Traffic Monitoring for Trunk groups

-It is started by entering ENTER TRAMON.

-The measurement is activate either for all the trunk groups in an exchange or for up to 4 traffic object groups .

-The threshold values entered define the interval in which Load or ATBT lies.

-One to three threshold levels for each function can be entered.

-The O/P will be done to the disk file every 15 minute every time the job is activated, with a range indicator which shows in which interval the value is placed.

-A Display of the measured data for the last interval can be obtained with DISPTRAMON: ….., ACTREC =Y;

-Traffic monitoring can be can be cancelled with CAN TRAMON.

Page 23: Traffic

Traffic Data Monitoring

2. Traffic Monitoring of the CP

-There is a measuring of all processors of the CP (BAP,CAP).

-The CP load is defined as the sum of the processor leads of all active processors divided by the sum of the active processors.

-The output of the measured values will be done to disk file every 15 minuted every time the job is active with range in indicator that shows in which threshold range the value is placed.

Page 24: Traffic

Traffic Data Monitoring

3 Coinbox Traffic Monitoring

The feature “Coinbox Monitoring”can be used to detect public coinboxes that are out of service i.e. no chargeable call has been originated from there during the last monitoring period of 15 minutes.

First of all a traffic object group must be created. A maximum of 512 coinboxes can be the members of one group.

4 DLU Traffic Monitoring

The feature can monitor the behaviour of entire DLU concerning

No. of rejected call set ups because of lack of DLU-LTG time slot, lack of LTG-SN speech channels . The parameter BLKTHR (0…99999) defines the threshold for blocked calls per 15 min interval.

The duration of all speech channels busy or all time slots busy,the parameter ACHBTTHR (0…900) defines the threshold.

Page 25: Traffic

TRAFFIC DATA MONITORING (TRUNK GROUPS)

ALTTC/A39336D1999/INDCPZ1V13313519/010 05-03-18 15:18:40

3437 OMT-00/ALTTC2 2900/00007

ENTRTRAMON:MTYP=TGRP,MNAME=ALTTC,ALLTGNO=Y,LOADTHR=500-700-900,ATBTTHR=50-100-150; EXEC'D

END JOB 3437

ALTTC/A39336D1999/INDCPZ1V13313519/010 05-03-18 15:20:09

3455 OMT-00/ALTTC2 2970/02698

DISPFILE:FILE=MD.; EXEC'D

USED SPACE : 3200 PAGES FOR 1 FILES

FILE GEN SIZE VSN000 VSN001 CLASS TYPE

--------+--------+-------+-------------+-------------+----+----

MD.TG.FR 3200 X NOT AVAILABLE PP SAM

END JOB 3455

 

Page 26: Traffic

TRAFFIC DATA MONITORING (TRUNK GROUPS)

3526<DISPTRAMON:MTYP=TGRP;ALTTC/A39336D1999/INDCPZ1V13313519/010 05-03-18 15:29:143526 OMT-00/ALTTC2 2904/07468 MASKNO:07468TRAFFIC MONITORING TASK: MTYP TGRP MASKNO:07469MNAME ALTTC DATE 05-03-18 TIME 15:18:40 STATUS A MASKNO:07470BEG TER MASKNO:07471IV MASKNO:07472PER MASKNO:07473 MASKNO:07485ALLTGNO LOADTHR ATBTTHR---------+-----------+----------- 500-700-900 50-100-150 MASKNO:07479END JOB 3526

Page 27: Traffic

TRAFFIC DATA MONITORING (TRUNK GROUPS)

ALTTC/A39336D1999/INDCPZ1V13313519/010 05-03-18 15:45:050086 2909/07468ACTUAL RECORDED REPORT DATE 05-03-18 TIME 15:45:00DATA QUALITY: SECURE MASKNO:07676 MASKNO:07480TGNO : OCDOT BCDOT7 ODX1 OMEERT ODX2 OPMODE : OG BW OG OG OG ----------+------+------+------+------+------+------+------LOAD 0 1000 0 362 0 MASKNO:07483LOADRG 1 4 1 1 1 MASKNO:07481ATBT 900 900 900 320 900 MASKNO:07482ATBTRG 4 4 4 4 4 MASKNO:07481ATBN 0 0 0 1 0 MASKNO:07483TC IC 10 MASKNO:07689CAL IC 0 TC OG 0 0 0 7 0 CAL OG 0 0 0 5 0 C%UNSUCC 0 0 0 60 0 MASKNO:07482C%ANS 0 0 0 100 0 MHT 0 0 0 326 0 CON LI 15 31 30 2 30 MASKNO:07483BLO LI 15 30 30 0 30 BLO TIME 0 0 0 0 0 MASKNO:07482

Page 28: Traffic

Traffic Structure Measurement

Unlike traffic measurement, traffic structure measurement is call-related, not object-related.

Traffic structure measurement may be related to the Trunk Group, Total Traffic, Originating Traffic, DLU or PA.

Traffic structure measurement is performed randomly. Thus, data is collected for every nth call only. The factor ‘n’ is specified as the parameter F, during order activation .

Once the ICTST buffer is full, its contents are transferred to the cyclic file IA.ICTST. The buffer data may also be transferred upon request using the command TRANS BUFFER.

Page 29: Traffic

MML commands for Traffic Structure Measurement

To activate traffic structure measurement

  ENTR TRST: TGNO = <trunk group number> orGRP = <traffic object group>TRST = ALL/ INC/ ORIG DLU = < DLU number>PA = < PA name >V52IF = < V5.2 Interface Number >F = <factor>,BEG = begin date,TER = termination date,IV = hh1 - mm1 - hh2 - mm2,PER = MO/ TU/ ………….. / SU/ WO/ HO ;

 ( max. 8 trunk groups for direct input, max.3 object groups may be linked)

Related Commands: DISP TRST, CAN TRST

Page 30: Traffic

Directory Number Observation

Like in traffic observation call related data is recorded but for each call.

The collected values provide the basis of subscriber behaviour. Subsequently the required resources and the expected flow of traffic can be estimated.

The directory number observation is performed on analog subscribers, PBX or ISDN subscribers

Once the ICDNB buffer is full, its contents are transferred to the cyclic file IA.ICDNB. The buffer data may also be transferred upon request using the command TRANS BUFFER.

Page 31: Traffic

  ENTR DNOBS:

GRP = ,

RREC = <requested records>

BEG = <yy> - <mm> - <dd>,

TER = <yy> - <mm>- <dd>,

IV = <hh1> - <mm1> - <hh2> - <mm2>,

PER = MU,

SU

WO

HO

Related Commands: DISP DNOBS, CAN DNOBS

MML commands for Directoty Number Observation