
120 Quality of Service
P0937663 02.0
If QoS levels of some or all routes fall short of being Good, evaluate options and costs for
upgrading the intranet. The evaluation often requires a link upgrade, a topology change, or
implementation of QoS in the network.
To maintain costs, you can accept a Fair QoS level for the time for a selected route. A calculated
trade-off in quality requires the installer or administrator monitor the QoS level, reset needs with
the end users, and respond to user feedback.
Implementing QoS in IP networks
Corporate intranets are developed to support data services. Accordingly, normal intranets are
designed to support a set of QoS objectives dictated by these data services.
When an intranet takes on a real-time service, users of that service set additional QoS objectives in
the intranet, Some of the targets can be less controlled compared with the targets set by current
services, while other targets are more controlled. For intranets not exposed to real-time services in
the past, but which but now need to deliver IP telephony traffic, QoS objectives for delay can set an
additional design restriction on the intranet.
One method is to subject all intranet traffic to additional QoS restrictions, and design the network
to the strictest QoS objectives. A exact plan to the design improves the quality of data services,
although most applications cannot identify a reduction of, say, 50 ms in delay. Improvement of the
network results in a network that is correctly planned for voice, but over planned for data services.
Another plan is to consider using QoS in the intranet. This provides a more cost-effective solution
to engineering the intranet for non-homogenous traffic types.
Traffic mix
This section describes QoS works with the IP telephony, and what new intranet-wide results can
occur.
Before putting into operation QoS in the network, determine the traffic mix of the network. QoS
depends on the process and ability to determine traffic (by class) so as to provide different services.
With an intranet designed only to deliver IP telephony traffic, where all traffic flows are equal
priority, there is no need to consider QoS. This network can have one class of traffic.
In most corporate environments, the intranet supports data and other services. When planning to
provide voice services over the intranet the installer determine the following:
• Is there existing QoS? What kind? IP telephony traffic must take advantage of established
mechanisms if possible.
• What is the traffic mix? If the IP telephony traffic is light compared to data traffic on the
intranet, then IP QoS can work. If IP telephony traffic is heavy, data services can be affected if
QoS is biased toward IP telephony traffic.
Comentarios a estos manuales