Control Dynamic System and Qos Manager Agent Over Ipv6 Networks: Intserv and Diffserv Approach in Access Nodes

Abstract

Abstract In the last ten years, the growth of IP-based data networks has led to the creation of new applications, which in turn have led to more data being sent. But the bandwidth of intradomain and interdomain transport networks has not grown at the same rate. In the last decade, the growth of IP-based data networks has led to the development of new applications that have increased the amount of data that can be sent. But the bandwidth of both intra-domain and inter-domain transport networks has not grown at the same rate. The present work is to look at how to provide QoS, which is a problem that is currently being looked into and for which there is no clear process or algorithm for a solution. A model that takes advantage of the features of the IPv6 protocol is also being used to find a solution. IPv6 is a very important protocol for the growth and development of Internet services and for supporting new services. But IPv6 doesn't have QoS in and of itself, even though it has different fields. This research aims to solve the QoS problem by trying to find the best way to combine the areas that IPv6 offers. The QoS manager agent was tested with MPLS in a congestion scenario. As a result, the values for jitter and delay for the highest priority flows got a lot better. High-priority flows are those that carry real-time traffic that can't handle delays or packet loss. The fact that the QoS manager agent didn't lose more than 3% of all packets, no matter how much traffic came into the node, shows that priority traffic is protected against network congestion problems. This feature is not present in the MPLS scenario, and as traffic grows, packet loss also grows. The QoS manager agent makes these characteristics better, but it makes them worse in low-level flows. Low-priority flows, on the other hand, are things like web browsing, file transfers, etc., that don't care much about time. The way these flows work is based on connection-oriented protocols like TCP. When packets are lost, the anti-congestion features of this protocol are turned on. The QoS manager agent doesn't have any way to measure incoming flows. This means that high throughput flows can fill up the classes, which goes against management policies, causes packet loss, and changes delay and jitter parameters. To improve the performance of the QoS manager agent in the future, it is suggested that a QoS provisioning protocol be created between a host and a border router. This would allow the agent to have more control over the flows that enter it and would improve the agent's performance.