Network traffic management

• US 5,371,731 A
• Filed: 05/10/1993
• Issued: 12/06/1994
• Est. Priority Date: 10/10/1990
• Status: Expired due to Fees

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Pratt, Christopher D., Platt, Amelia
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): BLUM, RUSSELL
• Application Number:
  US08/050,400
• Time in Patent Office: 575 Days
• Field of Search: 370/60, 370/94.1, 370/79, 370/13, 371/32
• US Class Current: 370/216
• CPC Class Codes: H04L 1/1806 Go-back-N protocols
• CPC Class Codes: H04L 1/1874 Buffer management
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/32 by discarding or delaying data units, e.g. packets or frames
• CPC Class Codes: H04L 47/33 using forward notification

Abstract

A network traffic management system and method for a relay-based communications network such as Frame Mode Bearer Service (FMBS) in which terminals (A and B) are linked by nodes (N) through which calls are routed, consists of setting a Recovery Needed flag at a node on detection of incorrect transmission of a frame or congestion at a node which discards the frame. The destination terminal (B) is notified by transmitting a null frame giving rise to a negative acknowledgement (NAK) received at the source terminal (A). The discarded frame is retransmitted with a Recovery flag set. At the node (N) the Recovery flag is detected and the frame is transmitted toward the destination terminal in the normal way. If the Recovery flag is not set and the Recovery Needed flag is set the frame is discarded. In this way, the rest of the network is not burdened with the transmission of frames that will be discarded by the destination terminal in any event until the discarded frame is correctly received. Furthermore, discarding frames that will not ultimately be transmitted successfully allows more accurate monitoring of successfully completed frame transmissions in order that more accurate billing of the customer can be employed.

Claims

1. A network traffic management system for a relay-based communications network comprising terminals (A and B), arranged to respond to receipt of blocks of information with positive or negative acknowledgement signals, as appropriate, and at least one node (N) through which blocks of information are routed between the said terminals, the system comprising:

means for discarding at a node a block transmitted from a source terminal to an addressed terminal, in the event that a predefined event has occurred;

means for setting a Recovery Needed flag at said node upon the occurrence of the predefined event;

means for transmitting to the addressed terminal an event occurrence signal such as to solicit a negative acknowledgement signal from the addressed terminal which is relayed to the source terminal;

means for retransmitting the discarded block with a set Recovery flag from the source terminal, in response to the receipt of the negative acknowledgement signal;

means for detecting the set Recovery flag at said node;

means at said node for transmitting the block towards addressed terminal in the event that the Recovery Needed flag and the Recovery flag are set, the means for discarding a block being arranged to discard any block in event that the Recovery Needed flag is set and the Recovery flag of that block is not set; and

means for resetting the Recovery Needed flag on detection of the set Recovery flag in a block at said node.

2. A system as claimed in claim 1, wherein said event occurrence signal is in the form of a null block.

3. A system as claimed in claim 1, in which the means for retransmitting is arranged to retransmit a group of discarded blocks with the first only of the group having the Recovery flag set, and the rest of the group having the Recovery flag not set.

4. A system as claimed claim 1, in which a plurality of blocks constitute a virtual call transmitted on a set route through the network, and in which said node assigns a specific Recovery Needed flag to each call.

5. A system as claimed in claim 1, in which the predefined event is congestion, or anticipated congestion, at said node.

6. A system as claimed in claim 1, in which the predefined event is reception of a block in error at said node.

7. A system as in claim 1 in combination with a frame mode bearer service network.

8. A method of network congestion management in a relay-based communications network comprising terminals (A and B), arranged to respond to receipt of blocks of information with positive or negative acknowledgement signals, as appropriate, and at least one node (N) through which blocks of information are routed between the said terminals, the method comprising:

discarding at a node a block transmitted from a source terminal to an addressed terminal, in the event that a predefined event has occurred;

setting a Recovery Needed flag at said node upon the occurrence of the predefined event;

transmitting to the addressed terminal an event occurrence signal such as to solicit a negative acknowledgement signal from the addressed terminal which is relayed to the source terminal;

retransmitting the discarded block with a set Recovery flag from the source Terminal, in response to receipt of the negative acknowledgement signal;

detecting the set Recovery flag at a node having a settable Recovery Needed flag;

transmitting a block from said node towards the addressed terminal in the event that the Recovery Needed flag and the Recovery flag are set;

discarding any block in the event that the Recovery Needed flag is set and the Recovery flag of that block is not set; and

resetting the Recovery Needed flag on detection of the set Recovery flag in a block at said node.

9. A method as claimed in claim 8, in which said signal transmitted by said node to the destination terminal is in the form of a null block.

10. A method as claimed in claim 8, in which a group of discarded blocks is retransmitted with the first only of the group having the Recovery flag set, and the rest of the group having the Recovery flag not set.

11. A method as claimed in claim 8, in which a plurality of blocks constitutes a virtual call transmitted on a set route through the network, and in which said node assigns a specific Recovery Needed flag to each call and for each direction of transmission.

12. A method as claimed in claim 8, in which the predefined event is congestion, or anticipated congestion, at said node.

13. A method as claimed in claim 8, in which the predefined event is reception of a block in error at said node.