Network Border Patrol: Preventing Congestion Collapse
ABSTRACT:-
The fundamental philosophy behind the Internet is expressed by the scalability argument: no protocol, mechanism, or service should be introduced into the Internet if it does not scale well. A key corollary to the scalability argument is the end-to-end argument: to maintain scalability, algorithmic complexity should be pushed to the edges of the network whenever possible.
Perhaps the best example of the Internet philosophy is TCP congestion control, which is implemented primarily through algorithms operating at end systems. Unfortunately, TCP congestion control also illustrates some of the shortcomings the end-to-end argument. As a result of its strict adherence to end-to-end congestion control, the current Internet suffers from main maladies: congestion collapse from undelivered packets.
The Internetâ„¢s excellent scalability and robustness result in part from the end-to-end nature of Internet congestion control. End-to-end congestion control algorithms alone, however, are unable to prevent the congestion collapse and unfairness created by applications that are unresponsive to network congestion. To address these maladies, we propose and investigate a novel congestion-avoidance mechanism called network border patrol (NBP).
NBP entails the exchange of feedback between routers at the borders of a network in order to detect and restrict unresponsive traffic flows before they enter the network, thereby preventing congestion within the network.
PROJECT MODULE:-
The various modules in the protocol are as follows
Module 1:- SOURCE MODULE:-
The task of this Module is to send the packet to the Ingress router.
Module 2:- INGRESS ROUTER MODULE:-
An edge router operating on a flow passing into a network is called an ingress router. NBP prevents congestion collapse through a combination of per-flow rate monitoring at egress routers and per-flow rate control at ingress routers. Rate control allows an ingress router to police the rate at which each flowâ„¢s packets enter the network. Ingress Router contains a flow classifier, per-flow traffic shapers (e.g., leaky buckets), a feedback controller, and a rate controller
Module 3:- ROUTER MODULE:-
The task of this Module is to accept the packet from the Ingress router and send it to the Egress router.
Module 4:- EGRESS ROUTER MODULE:-
An edge router operating on a flow passing out of a network is called an egress router. NBP prevents congestion collapse through a combination of per-flow rate monitoring at egress routers and per-flow rate control at ingress routers. Rate monitoring allows an egress router to determine how rapidly each flowâ„¢s packets are leaving the network. Rate monitored using a rate estimation algorithm such as the Time Sliding Window (TSW) algorithm. Egress Router contains a flow classifier, Rate monitor, a feedback controller.
Module 5:- DESTINATION MODULE:-
The task of this Module is to accept the packet from the Egress router and stored in a file in the Destination machine.
DATA FLOW DIAGRAM:
EXISTING SYSTEM
Packets are buffered in the routers present in the network which causes Congestion collapse from undelivered packets arises when bandwidth is continuously consumed by packets that are dropped before reaching their ultimate destinations.
Retransmission of undelivered packets is required to ensure no loss of data.
Unfair bandwidth allocation arises in the Internet due to the presence of undelivered packets.
PROPOSED SYSTEM
Buffering of packets in carried out in the edge routers rather than in the core routers.
The packets are sent into the network based on the capacity of the network and hence there is no possibility of any undelivered packets present in the network.
Absence of undelivered packets avoids overload due to retransmission.
Fair allocation of bandwidth is ensured.
SOFTWARE REQUIREMENTS:-
Java1.5 or More
Swings
Windows 98 or more.
HARDWARE REQUIREMENTS:-
Hard disk : 40 GB
RAM : 128mb
Processor : Pentium IV