Browse Prior Art Database

Traffic Saturation Control

IP.com Disclosure Number: IPCOM000082813D
Original Publication Date: 1975-Feb-01
Included in the Prior Art Database: 2005-Feb-28
Document File: 2 page(s) / 34K

Publishing Venue

IBM

Related People

Guillot, B: AUTHOR

Abstract

In a multiprivate branch exchange network there is a need to have a traffic saturation control program, in order that some kinds of calls be served in priority, in case of traffic saturation on the tie line bunch linking two exchanges.

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 100% of the total text.

Page 1 of 2

Traffic Saturation Control

In a multiprivate branch exchange network there is a need to have a traffic saturation control program, in order that some kinds of calls be served in priority, in case of traffic saturation on the tie line bunch linking two exchanges.

For this purpose two counts are associated to a bunch of tie lines, the dynamic count CI of idle tie lines of the bunch and a fixed count CR of reserved tie lines.

When a tie line (TL) in a bunch is to be seized (step 1), the traffic saturation control program examines a step 2 whether the request for a tie line comes from a priority call such as a transit call, an operator call or an inquiry, or from an extension.

In case of a priority call, the count CI is checked during step 3 and if it is different from 0 the seizure of any idle tie line is performed. If it is equal to 0, no seizure can be performed and a blocking occurs.

In case of an extension call, the program checks in step 4 whether the extension may have access to reserved tie lines. If yes, the call is handled as a priority call. If no, in step 5, the count CI - CR is checked and the seizure is performed only on condition that this count is different from 0.

1

Page 2 of 2

2

[This page contains 2 pictures or other non-text objects]