|
DBM is the latest generation of our equalized
traffic shaping technology. This feature ensures that no individual
or small group of users is able to saturate the WAN links with
so much application traffic that other users are unable to effectively
utilize the Internet and other cloud-based services.
Simple & Effective Traffic Shaping
Instead of attempting to classify every application which
may be used by an end user the EdgeXOS platforms takes a different
approach by tracking the session information and usage per session.
By tracking session information rather than the application
layer data the EdgeXOS appliance is able to stay ahead of changes
to peer-to-peer and other recreational applications and thus
provide a better shaping solution.
Session Flow Tracking
This is the ability to track client connections based on their
unique session IDs and certain other characteristics which can
uniquely identify the specific connection. Once identified the
session is tracked for overall usage as compared to other sessions
traversing the EdgeXOS appliance.
Dynamic Shaping
When sessions meet specifically defined criteria they are shaped
in order to maintain fair queuing for all other applications.
This shaping is dynamic and ensures that top users do not over-utilize
the available network bandwidth to the degree that other users
become unresponsive.
Why Application Classification Is Not Optimal...
The difference between session tracking and application classification
is that application classification requires constant updates
to a large database of applications. These updates often come
out weeks of not months after a new version of the application
comes out, which means that in some cases end-users can find
ways to get around application classification shaping appliances
by simply upgrading to the latest version.
Furthermore, some methods for classifying applications will
not work with the more sophisticated methods being employed
by the latest peer-to-peer applications. Unlike application
classification, session tracking does not care how the application
is defined, only that the session appears to be utilizing more
than it's fair share of bandwidth, and thus needs to be throttled.
This process guarantees more bandwidth for more end-users and
thus prevents most network congestion issues.
|