Browse Prior Art Database

Use of different triggered update thresholds for each traffic engineering class

IP.com Disclosure Number: IPCOM000028320D
Original Publication Date: 2004-Jun-25
Included in the Prior Art Database: 2004-Jun-25
Document File: 1 page(s) / 18K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

In communication networks information of the available bandwidth on a link is gathered periodically. Furthermore there are certain load thresholds implemented into traffic classes. If the current load on the link exceeds one of the implemented thresholds an update will be triggered. Every update causes additional traffic on the link. This denotes that the overhead traffic on the link due to the triggered updates can be quite high. It is proposed to define the threshold on a per traffic engineering class basis. A low threshold is set specifically for high priority traffic (e.g. voice-traffic). A high threshold is chosen for low priority traffic (e.g. web-traffic). The effort of this concept is to reduce the signaling traffic caused by the triggered updates to the minimum and avoiding impact on real-time services. High thresholds set for non real-time services increase the probability of call-retry attempts due to the increased availability of out-of-date bandwidth information. This concept still applies even in the case of having two thresholds, one low threshold and one high threshold. In that case there are two thresholds used in every traffic engineering class.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 88% of the total text.

Page 1 of 1

S

Use of different triggered update thresholds for each traffic engineering class

Idea: Richard Edwin, GB-Romsey; Andrew Reeve, GB-Romsey; Changpeng Fan, DE-Berlin

In communication networks information of the available bandwidth on a link is gathered periodically. Furthermore there are certain load thresholds implemented into traffic classes. If the current load on the link exceeds one of the implemented thresholds an update will be triggered. Every update causes additional traffic on the link. This denotes that the overhead traffic on the link due to the triggered updates can be quite high.

It is proposed to define the threshold on a per traffic engineering class basis. A low threshold is set specifically for high priority traffic (e.g. voice-traffic). A high threshold is chosen for low priority traffic (e.g. web-traffic). The effort of this concept is to reduce the signaling traffic caused by the triggered updates to the minimum and avoiding impact on real-time services. High thresholds set for non real- time services increase the probability of call-retry attempts due to the increased availability of out-of- date bandwidth information. This concept still applies even in the case of having two thresholds, one low threshold and one high threshold. In that case there are two thresholds used in every traffic engineering class.

An example of the use of this concept is to set the triggered update threshold for voice data to 60% and for non real-time data to 95%. Upd...