13.07.2015 Views

Praise for Fundamentals of WiMAX

Praise for Fundamentals of WiMAX

Praise for Fundamentals of WiMAX

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7.1 Quality <strong>of</strong> Service 225buffering packets be<strong>for</strong>e <strong>for</strong>warding. Overbuilding the network to provide higher bandwidthcapacity and larger buffers is an expensive and inefficient way to provide quality, particularlywhen the quality requirements are very high. There<strong>for</strong>e, more clever methods <strong>for</strong> providing QoSmust be devised and these methods must take into account the particular needs <strong>of</strong> the applicationor service and optimize the resources used. Different applications require a different mix <strong>of</strong>resources. For example, latency-intolerant applications require faster access to bandwidthresources and not memory, whereas latency-tolerant applications can use memory resources toavoid packets being dropped, while waiting <strong>for</strong> access to bandwidth resources. This fact may beexploited to deliver QoS efficiently. In short, a QoS-enabled network should provide guaranteesappropriate <strong>for</strong> various application and service types while making efficient use <strong>of</strong> networkresources.7.1.1 QoS Mechanisms in Packet NetworksProviding end-to-end QoS requires mechanisms in both the control plane and the data plane.Control plane mechanisms are needed to allow the users and the network to negotiate and agreeon the required QoS specifications, identify which users and applications are entitled to whattype <strong>of</strong> QoS, and let the network appropriately allocate resources to each service. Data planemechanisms are required to en<strong>for</strong>ce the agreed-on QoS requirements by controlling the amount<strong>of</strong> network resources that each application/user can consume.7.1.1.1 Control Plane MechanismsSuch mechanisms include QoS policy management, signaling, and admission control. QoS policymanagement is about defining and provisioning the various levels and types <strong>of</strong> QoS services,as well as managing which user and application gets what QoS. Figure 7.1 shows a generalizedpolicy-management system as described by IETF that may be used <strong>for</strong> managing QoS policies. 2The components <strong>of</strong> the system include (1) a policy repository, which typically is a directory containingthe policy data, such as username, applications, and the network resources to which theseare entitled; (2) policy decision points (PDP), which translate the higher-level policy data intospecific configuration in<strong>for</strong>mation <strong>for</strong> individual network nodes; (3) policy en<strong>for</strong>cement points(PEP), which are the data path nodes that act on the decisions made by the PDP; and (4) protocols<strong>for</strong> communication among the data store, PDP, and PEP. Examples <strong>of</strong> these protocolsinclude LDAP (lightweight directory access protocol) [30] <strong>for</strong> communication between datasource and PDP, and COPS (common open protocol services) [21] <strong>for</strong> communication betweenPDP to PEP.Signaling is about how a user communicates QoS requirements to a network. Signalingmechanisms may be either static or dynamic. In the static case, the PDP takes the high-level1. Note, though, that unlike wireless, other links are generally considered reliable. There<strong>for</strong>e, packetslosses there stem mostly from buffer overflow caused by congestion, not from channel-induced biterrors.2. A similar model is <strong>of</strong>ten used <strong>for</strong> security policies as well.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!