# Traffic Measurement in the System

This section discusses the manner in which traffic data is measured and tabulated in the system. It shows that the system, though not a non-blocking switch, offers virtual non-blocking characteristics to users.

In a large switching system, featuring a distributed processing architecture and the coexistence of voice and data switching facilities, traffic analysis appears complex. However, the design of the system greatly simplifies traffic analysis requirements through a virtually non-blocking switching arrangement where only a minimum of components are traffic-dependent, and that the resulting analysis of traffic data is very simple. Two terms of importance in traffic measurement will be used in the following paragraphs and are defined as follows:

1. Period. This term refers to the duration of an individual traffic measurement period. This period is the amount of time over which traffic data will be accumulated and can be set by the user to be either 15, 30, or 60 minutes. At the end of each period, the system produces a traffic report.

2. Time Slot. This term refers to the span of time during which traffic data will be collected on a given day. The time slot of a traffic session is measured in periods. For example, if measurements are to take place from 8:00 A.M. to 5:00 P.M. and reports are produced every 30 minutes, then the traffic session is said to consist of periods 30 minutes in length and has a time slot of 18 periods (9 hours).

### System Call Processing

Traffic Measurement in the system shows the hardware and software components that are relevant to traffic measurement. The software components are shown within the dashed box representing the system. External components involved in traffic measurement and monitoring include all peripheral devices (voice and data stations and trunks) as well as the maintenance devices (maintenance terminal and printers). In the course of call processing, traffic data is gathered as follows:

1. As service requests are generated from either telephones, data stations or trunks, the Call Processing module responds and establishes connections through the circuit switch matrix to other peripheral devices.

2. As each request is served by Call Processing, the Performance Monitor module records the event (peg count), the state of the connection (successful or busy), and the duration of the connection.

3. The Performance Monitor continually records data, storing it in internal buffers.

4. At the end of each traffic measurement period, the data is transferred to the Traffic Buffer where the information is processed by the Traffic Measurement module.

5. The Traffic Measurement module then generates a file in the system Mass Storage devices which represents a formatted and printable traffic report for a given period.

6. The traffic report file lists peg count, usage (Erlangs or CCS) and number of circuits used in comparison to the number of circuits available (for outgoing trunk groups). The traffic report file also records traffic on individual trunks, as well as call processing statistics for each Attendant Group.

### Call Processing and Traffic Measurement

The various inter-connections allowed by the Call Processing module which are recorded by the Performance Monitor are listed in the following table. The data collected concerns trunks, DTMF receivers. The traffic reports provide a complete record of traffic on individual circuits and groups. The trunk-related information is relevant in streamlining the performance of Automatic Route Selection (ARS) by providing the traffic analyst with the ability to evaluate the effectiveness of trunk grouping by Route and the overflow capabilities of Route Lists.

Traffic Related Inter-connections
From Device | To Device | Comments
Any station (voice or data) | Trunk Group | Accessed through ARS or System Speed Call
Trunk | Trunk Group | Tandeming
Trunk | Any station | DID, CO or tie trunks
Trunk | Attendant Console | Attendant-handled trunks
Any ONS/OPS station or DTMF signaling trunk | DTMF Receiver | Dialing phase of a call

### Message Summary

The following table lists all status and error messages which may appear at the Maintenance Terminal during traffic measurement.

Traffic Messages
Message | Meaning
TRAFFIC DELETE COMMAND |
Traffic file deleted. | This message appears once for each file deleted.
Traffic file could not be deleted. | The file could not be deleted due to file system errors.
No traffic files deleted. | No files matching the specified name were found.
TRAFFIC FILES COMMAND |
No traffic files found. | No traffic files currently exist in mass storage.
TRAFFIC PRINT COMMAND |
No files to print. | The report file(s) requested were not found. Use TRAFFIC FILES to verify the report name(s) and resubmit.
File <filename> queued for printing. | This message appears for each file sent to the printer.
File <filename> does NOT exist. | The report file was lost or deleted before it could be printed.
Printer <filename> <printername> does NOT exist. | Printer name not valid. Verify the printer name and resubmit.
Printer Queue is full. File <filename> not queued. | Ten files already queued to print; cannot queue any more files.
Cannot execute command. Traffic Print in progress. | Previous TRAFFIC PRINT command not complete, cannot print any more files at this time.
Cannot continue printing of files, file error. | Internal printer error or file is unprintable.
TRAFFIC STOP COMMAND |
TRAFPROC: Data collection not active. | No traffic data collection in progress; no report formatted.
TRAFPROC: Data collection stopped. Report initiated. | Traffic report being started for traffic period just ended.
TRAFORM: Traffic report for period < n> of session < n> begins. | Traffic report being prepared for specified traffic reporting period.
TRAFORM: Traffic report for period < n> of session < n> completed. | Traffic reported completed for specified traffic reporting period.
MISCELLANEOUS MESSAGES |
TRAFPROC: System time change or TRAFFIC form change detected. Period < n>of session < n> not reported. | System or a traffic form change occurred during a traffic period; no report prepared.
Active traffic commands are not allowed on the inactive plane. | Only the STATUS, FILE, HELP, and PRINT commands may be issued from the inactive plane. All other commands are disallowed.
ERROR - incomplete command | The command entered did not have the required options.
ERROR - invalid keyword | The option to the command was incorrectly specified.