In a typical network, the delay sensitive traffic like video conferencing traffic and Voip calls flow together with the non-delay sensitive and bandwidth hungry traffic such as FTP and HTTP. At peak traffic conditions the FTP and HTTP traffic will try to take as much bandwidth as possible leading to the degradation of the voice and video quality. A better solution to bandwidth over-provisioning in this case is to put some kind of cap to the amount of bandwidth an application can take without disturbing the delay sensitive traffic. In other words, we can allocate a fixed amount of bandwidth to different traffic types. However, this over-provising causes another problem referred to as idle bandwith, if a specific traffic type is inactive for a given time.
The best possible way is to provide bandwidth as needed. This requires the network elements to understand and change its configuration depending upon the traffic patterns according to the policy of the organisation. Our framework makes this possible, which otherwise need repetitive skilled human intervention.