EP0741475A2
Expired / Lapsed
EP
⏱️ 0.0 years remaining
Communication system with tagging facility
Assignee: Koninklijke KPN NV
•
Filing: 1995-10-06
•
Granted: —
•
Expires: 2015-10-06
Abstract
Abstract Communication system, capable for the transmission of datacells via virtual channels, with a priority code as well as a first tagging code, both being assignable to the datacells of such channel. The system comprising bandwidth control devices at network edges, for the enforcement of the allowed cellrate, such bandwidth control device admitting said datacells as long as the actual cellrate does not exceed said allowed cellrate, or, if the actual cellrate does exceed said allowed cellrate, admitting said datacells, however, after modifying its priority code into a lower priority code. For use in a bidirectional set of virtual channels, comprising a first, forward channel from a calling user to a called user and a second, backward channel from the called user to the calling user, a second tagging code is assignable to said datacells of the first channel, which second tagging code relates to said backward channel. In the octet 19.1 of the ATM Traffic Descriptor information element there are two spare bits, named Tf (Tagging Forward) and Tb (Tagging Backward), used for the tagging option. These two bits are coded in a special way, serving the purpose of locally enabling the tagging option along the whole bidirectional path.
Inventors
- 👤 Azeddine Benchellal
Bibliographic Details
Application Number
—
Jurisdiction
EP
Data Source
google_patents
Last Synchronized
2026-10-29 00:45
CPC Classifications
H; H04; H04L; H04L12/00; H04L12/54; H04L12/56; H04L12/5601; H04L12/5602; H04L2012/5629; H04L2012/563; H04L2012/5631; H04L2012/5636; H04L2012/5638; H04L2012/5646; H04L2012/5651
Claims Analysis
Total Claims: 3
Claim 1
Independent Claim
151 words
Communication system, capable for the transmission of datacells via virtual channels, with a priority code as well as a first tagging code, both being assignable to the datacells of such channel, the system comprising bandwidth control devices at network edges, for the enforcement of the allowed cellrate, such bandwidth control device admitting said datacells as long as the actual cellrate does not exceed said allowed cellrate, or, if the actual cellrate does exceed said allowed cellrate, admitting said datacells, however, after modifying its priority code into a lower priority code, characterized in that , for use in a bidirectional set of virtual channels, comprising a first, forward channel from a calling user to a called user and a second, backward channel from the called user to the calling user, a second tagging code is assignable to said datacells of the first channel, which second tagging code relates to said backward channel.
Claim 2
Dependent Claim
433 words
Communication system according to claim 1, characterized in that , at the calling user's end: the calling user, by use of the first tagging code and second tagging code, may indicate 'tagging requested' or 'tagging not allowed' for the forward and backward direction; when the calling user has indicated in the first tagging code and second tagging code 'tagging requested' and the called user requests tagging for the backward direction and the network supports tagging in the forward and backward direction, the network shall upon successful call establishment include an information code in the CONNECT message, and set the first tagging code and second tagging code subfields to 'tagging applied', and apply tagging for the user plane traffic in the forward direction and the backward direction; when the calling user has indicated in second tagging code subfield 'tagging requested' and the called user does not request tagging for the backward direction and the network supports tagging in the backward direction, the network shall upon successful call establishment not apply tagging in the backward direction, include an information code in the CONNECT message, and set the second tagging code subfield to 'tagging not applied'; when the calling user has indicated in first tagging code subfield 'tagging not allowed' and the network supports tagging in the forward direction, the network shall upon successful call establishment not apply tagging in the forward direction, include an information code in the CONNECT message, and set the first tagging code subfield to 'tagging not applied'; when the calling user has indicated in second tagging code subfield 'tagging not allowed' and the called user requests tagging for the backward direction and the network supports tagging in the backward direction, the network shall upon successful call establishment apply tagging in the backward direction, include an information code in the CONNECT message, and set the second tagging code subfield to 'tagging applied' (see Note 2); if the network does not support tagging in the forward and backward direction, the network shall not apply tagging and shall: - include an information code in the CONNECT message and set the first tagging code and second tagging code subfields to 'tagging not applied', or - not include the Traffic Management Options field in the information code in the CONNECT message, or - not include the information code in the CONNECT message; if the network does not support tagging in the forward or backward direction, the network shall not apply tagging and shall include an information code in the CONNECT message and set the first tagging code or second tagging code subfield to 'tagging not applied';
Claim 3
Dependent Claim
341 words
Communication system according to claim 1, characterized in that , at the called user's end: if the network supports tagging in the backward direction, the network shall send a SETUP message to the called user and set the subfield second tagging code to 'tagging allowed' in the information code; if the calling user indicates in the second tagging code subfield 'tagging requested' and the network supports tagging in the backward direction, the network shall send a SETUP message to the called user and set the subfield second tagging code to 'tagging allowed' in the information code; if the calling user indicates in second tagging code subfield 'tagging not allowed' and the network supports tagging in the backward direction, the network shall send a SETUP message to the called user and set the subfield second tagging code to 'tagging not allowed' in the information code; if the network does not support the tagging option, the network shall not include the second tagging code subfield in the information code in the SETUP message; When the called user receives an information code in the SETUP message with second tagging code subfield set to 'tagging allowed', the user may upon successful call establishment include an information code in the CONNECT message with the second tagging code subfield set to 'tagging requested' or 'tagging not requested'; when the called user receives an information code in the SETUP message with second tagging code subfield set to 'tagging not allowed', the user may upon successful call establishment: - include an information code in the CONNECT message with the second tagging code subfield set to 'tagging not requested', or - include an information code in the CONNECT message without the Traffic Management Options field, or - not include an information code in the CONNECT message; upon receipt of the CONNECT message with the second tagging code subfield set to 'tagging requested' in the information code, the network shall apply tagging for the user plane traffic in the backward direction; In all other cases the network shall not apply tagging.
References Cited (Backward Citations)
US4769810A
Cited
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.