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.

226 Chapter 7 • Networking and Services Aspects <strong>of</strong> Broadband WirelessPolicyDecisionPoint (PDP)PolicyDataSenderPEPPEPReceiverPEPPolicy En<strong>for</strong>cement Point (PEP)Data PathControl PathFigure 7.1 A QoS policy-management systempolicy in<strong>for</strong>mation in the policy data and creates configuration in<strong>for</strong>mation that is pushed down toeach PEP that en<strong>for</strong>ces the policies. Policy data is usually created based on service-level agreements(SLA) between the user and the network provider. In the dynamic case, QoS requirementsare signaled by the user or application as needed just prior to the data flow. RSVP (resource reservationprotocol) is a protocol used <strong>for</strong> such signaling and is covered in Section 7.1.2. When arequest <strong>for</strong> a certain QoS arrives at the PEP, it checks with the PDP <strong>for</strong> approval, and, if accepted,allocates the necessary resources <strong>for</strong> delivering the requested QoS.Admission control, the other important control plane function, is the ability <strong>of</strong> a network tocontrol admission to new traffic, based on resource availability. Admission control is necessaryto ensure that new traffic is admitted into the network only if such admission will not compromisethe per<strong>for</strong>mance <strong>of</strong> existing traffic. Admission control may be done either at each node ona per-hop basis, just at the ingress-edge node, or by a centralized system that has knowledge <strong>of</strong>the end-to-end network conditions.7.1.1.2 Data Plane MechanismsThese methods en<strong>for</strong>ce the agreed-on QoS by classifying the incoming packets into severalqueues and allocating appropriate resources to each queue. Classification is done by inspectingthe headers <strong>of</strong> incoming packets; resource allocation is done by using appropriate schedulingalgorithms and buffer-management techniques <strong>for</strong> storing and <strong>for</strong>warding packets in each queue.There are fundamentally two different approaches to how these queues are defined. The firstapproach called per-flow handling, is to have a separate queue <strong>for</strong> each individual session orflow. In this case, packets belonging to a given session or flow need to be uniquely identified.For IP traffic, this is typically the five fields in the IP header: source and destination IPaddresses, source and destination port addresses, and transport-layer protocol fields. The IntServmethods defined by the IETF use per-flow handling <strong>of</strong> IP packets. From an end user perspective,

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

Saved successfully!

Ooh no, something went wrong!