Home > Articles > Software Development & Management

Quality of Service, Part 2 of 2: Managing Enterprise QoS

📄 Contents

  1. Elements of Enterprise QoS
  2. Conclusion
  3. References
In the conclusion of his two-part series on quality of service (QoS), network management specialist Stephen Morris discusses the issues of enterprise QoS management.
Like this article? We recommend

Consolidation of networks into IP-based cores is occurring in enterprises as well as service providers. The IP core is becoming a service platform, the resources of which are shared by a growing range of legacy and real-time applications. Downtime equates to revenue loss, and this fact is reflected in the appearance of financial rebate service-level agreements. So, how can the elements of QoS be managed effectively? To an extent, the tools are good if you stick with one vendor, but for multivendor networks the problem is more difficult.

As I described in the first article in this series, QoS management breaks down into specific elements: throughput, availability, delay, delay variation, and loss. The management system user aims to provide the best possible mix of these attributes.

Elements of Enterprise QoS

The previous article looked at voice-over-IP (VoIP) and the sources of delay that occur as a natural part of that technology. As far as possible, the designer tries to minimize the overall delay, which is the sum of the following delay types: coder, packetization, serialization, output queuing, WAN, and dejitter delay.

Voice service straddles both the analog and digital worlds; that is, traffic starts off in analog form, is made digital, is transmitted through the network, and then finishes out once again in analog form at the receiving end. Voice service typically (although not necessarily) employs a range of equipment types including legacy PBX/telephone/TDM elements. The provision of QoS for such a complex service is a challenging undertaking. Given the real-time nature of voice, one of the key QoS elements is delay. However, that's just one aspect of managing this class of network service. Figure 1 illustrates some of the other elements of QoS.

Figure 1Figure 1 An IP/MPLS virtual private network (VPN).

Figure 1 illustrates an IP VPN with two sites interconnected by a VPN service provider. A production system would have many more VPNs and sites—possibly hundreds of thousands of each. The network management system (NMS) is used to provision, monitor, and update the network. Each site has one or more CE boxes (customer edge routers) that connect to the adjacent service provider PE (provider edge) box. The PE devices are in turn connected to core P devices (provider nodes that deliver a traffic transit service). In many instances, all three device types are owned and managed by the service provider. This setup frees the enterprise from concerns about the technology—it just uses and pays a fixed monthly fee for the service.

There are at least four main elements to delivering enterprise QoS successfully:

  1. Network engineering

  2. Traffic engineering (TE)

  3. QoS technologies

  4. Network operation

An important point about these steps is that they are generally iterative. An example is step 2 (traffic engineering), when a network operator wants to partition the network into specific paths. For example, LSP A in Figure 1 is for a real-time service, and LSP B is for a non–real-time service. The operator may simply begin with best-effort service for both and employ traffic analysis before deciding on an appropriate TE setup. Once the paths have been arrived at and provisioned in the network, the associated QoS resources (DiffServ markings, bandwidth, queuing assignments, scheduling details, and so on) are assigned in step 3 (QoS technologies). Again, the traffic may be monitored to determine whether links have sufficient resources for the imposed traffic. This might necessitate further path definitions and QoS assignments; that is, revisiting steps 2–3.

Finally, the network goes into service (step 4) and, as in the test phase, the earlier steps may have to be revisited. And so it goes. Let's take a closer look at the steps involved.

Step 1: Network Engineering

Closely tied with planning, network engineering consists of putting together a network, that is, physically connecting the network devices—servers, client machines, routers, switches, hubs, service provider interconnects, and so on. Software and configuration data must be loaded into the devices. Then the interfaces must be configured, along with the associated signaling and routing protocols. Network engineering can be said to bring the network into a raw state of operational readiness. Many small LANs go straight into operation at this point. For larger networks, more work is needed (steps 2–4).

Step 2: Traffic Engineering

If network engineering puts the bandwidth into the network, traffic engineering is the process of "putting the traffic where the bandwidth is"; this means directing network traffic into devices and links that have sufficient resources to handle it.

Different technologies have their own unique TE facilities. For example, multiprotocol label switching (MPLS) provides what are called explicit route objects (ERO) to facilitate TE by allowing the operator to define a set of MPLS node hops. [1] The ERO is a little like a map for directing the traffic along the specified path.

An LSP (as in Figure 1) can then be created to follow the path specified by the ERO. So, to get from PE1 to PE2 in Figure 1, incoming traffic from VPN A, Site 1 is pushed into the explicitly routed LSP A. This control of routing paths gives MPLS great TE power and allows it to compete with legacy features of ATM (designated transit lists—DTLs—are the ATM equivalent of MPLS EROs). This is also a motivator for adopting MPLS.

TE provides the means for carving up a network core into a set of distinct paths, each one for a different type of traffic: real-time VoIP, non–real-time email, and so on. TE can be thought of as a high-granularity mechanism. The individual node treatment of traffic provides a finer level of granularity, as shown in the next section.

Step 3: QoS Technologies

The area of QoS is almost a science in its own right. The MPLS-OPS mailing list frequently has spirited discussions that touch on this field. These conversations get so complex that they generally are taken offline after just a few contributions!

QoS has a large body of active research of great interest to network equipment vendors; for example, witness Cisco's acquisition of PARC Technologies. The latter has expertise in the area of network-path placement with respect to a set of constraints (such as bandwidth). An allied area is the detection of different traffic types as close as possible to the edge of the network. If it's possible to separate the traffic types at the network edge, each traffic type can be allocated its own specific QoS treatment, such as pushing it into a given LSP.

From the end user's perspective, QoS is the final result of many careful network operator TE and device-level configurations. As we saw in the previous article, queues are a key element in QoS provisioning. If a given traffic type (such as VoIP) can skip the queue ahead of a traffic type with less stringent QoS needs (such as email), we have a useful scheme for providing definable QoS levels. This is the way in which DiffServ can be used: Packets are marked in the IP header DiffServ field (a six-bit field) and this value then dictates the downstream treatment. In Figure 1, the DiffServ markings could be applied on link A or B by the CE routers. With respect to the CE devices, the downstream routers are the adjacent PEs (and core P nodes). The PEs (followed by the Ps) then provide the next step in the QoS process.

Priority queues in supermarkets (or other stores) can produce happy customers; the same analogy obtains for network devices. If one type of traffic can get through a queue ahead of the others, there's a good chance that the originator and receiver of that traffic will enjoy a decent QoS level.

It's no coincidence that PE devices tend to be complex, high-performance, multi-technology switch routers that implement options for IP, MPLS, ATM, frame relay, SONET/SDH, etc.

Device Simplicity

I'm often struck by the conceptual simplicity of network devices such as those in Figure 1. Traffic arrives on a given interface, some technology-specific (IP, MPLS, ATM, etc.) lookup/manipulation occurs, and the traffic is then pushed out an egress interface toward an adjacent device. The same process occurs all the way to the destination. Clearly, many other details [1] are required for a complete picture, such as DiffServ/IntServ, policing, rate limiting, shaping, scheduling classes, per-hop behaviors, and so forth, but the big picture is essentially one of simplicity.

Step 4: Network Operation

The final step we've identified is network operation—where the service provider actually carries real customer traffic and attempts to supply the required QoS. At this point, the service-level agreement (SLA) comes into play. This is the contractual specification of how well the service provider will attempt to handle the customer service. As usual, network management plays a key role, with the NMS handling these processes (among others):

  • Fault monitoring and repair

  • Performance monitoring

If persistent problems are occurring—for example, if LSP A in Figure 1 is dropping packets due to congestion—there may be a need for extra resources. On the other hand, LSP A may be correctly forwarding all its traffic, but not quickly enough; in other words, the performance may not be as required. Both situations may warrant SLA rebates to customers, so the service provider may have to use the information gleaned from the operational network to reengineer the LSP or the links it traverses.

The important point is that the process is iterative. Traditionally, the areas of fault analysis and performance management have been seen as the baseline. As networks are now mission-critical enterprise elements, the network management system is an indispensable business-supporting technology. Ideally, the NMS should provide a network technology–independent facility for provisioning and operating a network. Essentially, the operator specifies the required policies; QoS, TE, and the NMS should take care of the rest. The low-level details should be handled by the NMS, freeing the network operator to focus on higher value-added issues, such as these:

  • Overbooking resources to improve utilization

  • Backup resources to protect critical services—tunnel instances, fast reroute

The reality of commercial network management products is not so rosy. Many devices still have to be configured manually. Keeping some NMS applications and associated devices up and running in complex networks is the equivalent of a tightrope act without a safety net. Much progress is needed in this area.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020