Browse Prior Art Database

Programmable Process for Identifying Time Spent by Each Component in a Communication Line Session Between Two (Or More) Devices

IP.com Disclosure Number: IPCOM000041454D
Original Publication Date: 1984-Jan-01
Included in the Prior Art Database: 2005-Feb-02
Document File: 3 page(s) / 63K

Publishing Venue

IBM

Related People

Elrod, TP: AUTHOR [+3]

Abstract

This article describes a programmable process for analyzing performance in a communications system to identify the time used by each component of the communication session so that bottlenecks can be minimized. For analysis of data throughput between the Data Sender and the Data Receiver, the total session/network time for a data communication operation, such as an office system sending a document to a remote printer, must be broken into (at least) the following components: 1) Data Sender Process Time - Session/network time spent waiting for the Data Sender to prepare more data to be sent. 2) Modem ("turnaround") time 3) Data transmission time 4) Data Receiver Process Time - Time spent while the session/network is waiting on data acknowledgement/receipt indication (e.g.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 3

Programmable Process for Identifying Time Spent by Each Component in a Communication Line Session Between Two (Or More) Devices

This article describes a programmable process for analyzing performance in a communications system to identify the time used by each component of the communication session so that bottlenecks can be minimized. For analysis of data throughput between the Data Sender and the Data Receiver, the total session/network time for a data communication operation, such as an office system sending a document to a remote printer, must be broken into (at least) the following components: 1) Data Sender Process Time - Session/network time spent waiting for the Data Sender to prepare more data to be

sent. 2) Modem ("turnaround") time 3) Data transmission time
4) Data Receiver Process Time - Time spent while the

session/network is waiting on data

acknowledgement/receipt indication (e.g., positive response)

from the Data Receiver after transmission finishes for the

last data buffer sent. This time is spent by the Data

Receiver to sufficiently process the previously-sent data so

that buffers are now available for new data. 5) Time Spent Between Documents - This time includes sender/receiver process delays (e.g., "clean-up," converting

next document for transmission, etc.) and data transfer time

to complete handshaking (headers, etc.) for next document. The implementation of the process requires a communication line monitor that can be programmed to dynamically count, measure time, and sum the time into the above components, using the actual line data in real time. The results are displayed immediately after the test is complete. Modem time is easily calculated by counting the number of filler bytes between Request-to-Send (RTS) and Clear-to-Send (CTS) records. That number is multiplied by the factor which represents the amount of time per byte which is applicable to the line speed used (e.g., 1.667 milliseconds per byte for a 4800 bps line). Data transmission time is easily calculated in the same manner after counting the bytes between "start-of-data" and "end-of-data" rec...