final Year Projects, Final Year Projects in Chennai, Software Projects, Embedded Projects, Microcontrollers Projects, DSP Projects, VLSI Projects, Matlab Projects, Java Projects, .NET Projects, IEEE Projects, IEEE 2009 Projects, IEEE 2009 Projects, Software, IEEE 2009 Projects, Embedded, Software IEEE 2009 Projects, Embedded IEEE 2009 Projects, Final Year Project Titles, Final Year Project Reports, Final Year Project Review, Robotics Projects, Mechanical Projects, Electrical Projects, Power Electronics Projects, Power System Projects, Model Projects, Java Projects, J2EE Projects, Engineering Projects, Student Projects, Engineering College Projects, MCA Projects, BE Projects, BTech Projects, ME Projects, MTech Projects, Wireless Networks Projects, Network Security Projects, Networking Projects, final year projects, ieee projects, student projects, college projects, ieee projects in chennai, java projects, software ieee projects, embedded ieee projects, "ieee2009projects", "final year projects", "ieee projects", "Engineering Projects", "Final Year Projects in Chennai", "Final year Projects at Chennai", Java Projects, ASP.NET Projects, VB.NET Projects, C# Projects, Visual C++ Projects, Matlab Projects, NS2 Projects, C Projects, Microcontroller Projects, ATMEL Projects, PIC Projects, ARM Projects, DSP Projects, VLSI Projects, FPGA Projects, CPLD Projects, Power Electronics Projects, Electrical Projects, Robotics Projects, Solor Projects, MEMS Projects, J2EE Projects, J2ME Projects, AJAX Projects, Structs Projects, EJB Projects, Real Time Projects, Live Projects, Student Projects, Engineering Projects, MCA Projects, MBA Projects, College Projects, BE Projects, BTech Projects, ME Projects, MTech Projects, M.Sc Projects, Final Year Java Projects, Final Year ASP.NET Projects, Final Year VB.NET Projects, Final Year C# Projects, Final Year Visual C++ Projects, Final Year Matlab Projects, Final Year NS2 Projects, Final Year C Projects, Final Year Microcontroller Projects, Final Year ATMEL Projects, Final Year PIC Projects, Final Year ARM Projects, Final Year DSP Projects, Final Year VLSI Projects, Final Year FPGA Projects, Final Year CPLD Projects, Final Year Power Electronics Projects, Final Year Electrical Projects, Final Year Robotics Projects, Final Year Solor Projects, Final Year MEMS Projects, Final Year J2EE Projects, Final Year J2ME Projects, Final Year AJAX Projects, Final Year Structs Projects, Final Year EJB Projects, Final Year Real Time Projects, Final Year Live Projects, Final Year Student Projects, Final Year Engineering Projects, Final Year MCA Projects, Final Year MBA Projects, Final Year College Projects, Final Year BE Projects, Final Year BTech Projects, Final Year ME Projects, Final Year MTech Projects, Final Year M.Sc Projects, IEEE Java Projects, ASP.NET Projects, VB.NET Projects, C# Projects, Visual C++ Projects, Matlab Projects, NS2 Projects, C Projects, Microcontroller Projects, ATMEL Projects, PIC Projects, ARM Projects, DSP Projects, VLSI Projects, FPGA Projects, CPLD Projects, Power Electronics Projects, Electrical Projects, Robotics Projects, Solor Projects, MEMS Projects, J2EE Projects, J2ME Projects, AJAX Projects, Structs Projects, EJB Projects, Real Time Projects, Live Projects, Student Projects, Engineering Projects, MCA Projects, MBA Projects, College Projects, BE Projects, BTech Projects, ME Projects, MTech Projects, M.Sc Projects, IEEE 2009 Java Projects, IEEE 2009 ASP.NET Projects, IEEE 2009 VB.NET Projects, IEEE 2009 C# Projects, IEEE 2009 Visual C++ Projects, IEEE 2009 Matlab Projects, IEEE 2009 NS2 Projects, IEEE 2009 C Projects, IEEE 2009 Microcontroller Projects, IEEE 2009 ATMEL Projects, IEEE 2009 PIC Projects, IEEE 2009 ARM Projects, IEEE 2009 DSP Projects, IEEE 2009 VLSI Projects, IEEE 2009 FPGA Projects, IEEE 2009 CPLD Projects, IEEE 2009 Power Electronics Projects, IEEE 2009 Electrical Projects, IEEE 2009 Robotics Projects, IEEE 2009 Solor Projects, IEEE 2009 MEMS Projects, IEEE 2009 J2EE P
1. NETWORK BORDER PATROL
PREVENTING CONGESTION COLLAPSE
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 MODULES
The various modules in the protocol are as follows
Module 1:- SOURCE MODULE
Module 2:- INGRESS ROUTER MODULE
Module 3:- ROUTER MODULE
Module 4:- EGRESS ROUTER MODULE
Module 5:- DESTINATION MODULE
2. • SOURCE MODULE
The task of this Module is to send the packet to the Ingress router.
• 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
• ROUTER MODULE
The task of this Module is to accept the packet from the Ingress router and
send it to the Egress router.
• 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.
• 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.
ADVANTAGES OF 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.
3. DRAWBACKS OF EXISTING SYSTEM (ATM)
• 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.
SOFTWARE REQUIREMENTS:-
• Java1.3 or More
• Swings
• Windows 98 or more.
HARDWARE REQUIREMENTS:-
• Hard disk : 40 GB
• RAM : 128mb
• Processor : Pentium
APPLICATIONS
This concept can be applied in LAN, WAN, MAN and in Internet in order to
prevent congestion collapse in the network.
SOURCE MODULE
• Input Parameters
• Source Machine Name is retrieved from the OS
• Destination Machine Name is typed by User
• Message is typed by User
• Output Parameters
• Data Packets
INGRESS MODULE
• Input Parameters
• Data Packets from Source Machine
• Backward feedback from the Router
4. • Output Parameters
• Data Packets
• Forward feedback
ROUTER MODULE
• Input Parameters
• Data Packets from Ingress Machine
• Forward feedback from the Router or Ingress Router
• Backward feedback from the Router or Egress Router
• Hop count
• Output Parameters
• Data Packets
• Forward feedback
• Incremented Hop count
• Backward feedback
EGRESS MODULE
• Input Parameters
• Data Packets from Router
• Forward feedback from the Router
• Output Parameters
• Data Packets
• Backward feedback
DESTINATION MODULE
• Message received from the egress router will be stored in the
corresponding folder as a text file depends upon the Source Machine
Name