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.

10.7 Quality-<strong>of</strong>-Service Architecture 351AuthenticationRelayKey ReceiverAuthenticationRelay ProtocolAK TransferProtocolAuthenticatorKeyDistributorAuthenticationRelayBase StationKey ReceiverAuthenticationRelay ProtocolAK TransferProtocolAuthenticatorSingleDeviceKeyDistributor(a)(b)Figure 10.8 ASN security architecture and deployment models: (a) integrated deployment modeland (b) stand-alone deployment modelFigure 10.9 shows the proposed QoS functional architecture as proposed by the <strong>WiMAX</strong>NWG. This architecture supports the dynamic creation, admission, activation, modification, anddeletion <strong>of</strong> service flows. The important functional entities in the architecture are as follows:Policy function. The policy function (PF) and a database reside in the home NSP. The PFcontains the general and application-dependent policy rules <strong>of</strong> the NSP. The PF database mayoptionally be provisioned by an AAA server with user-related QoS pr<strong>of</strong>iles and policies. The PFis responsible <strong>for</strong> evaluating a service request it receives against the provisioned. Servicerequests to the PF may come from the service flow authorization (SFA) function or from anapplication function (AF), depending on how the service flows are triggered.AAA server. The user QoS pr<strong>of</strong>iles and associated policy rules are stored in the AAAserver. User QoS in<strong>for</strong>mation is downloaded to an SFA at network entry as part <strong>of</strong> the authenticationand authorization procedure. The SFA then evaluates incoming service requests againstthis downloaded user pr<strong>of</strong>ile to determine handling. Alternatively, the AAA server can provisionthe PF with subscriber-related QoS in<strong>for</strong>mation. In this case, the home PF determines howincoming service flows are handled.Service flow management. The service flow management (SFM) is a logical entity in theBS that is responsible <strong>for</strong> the creation, admission, activation, modification, and deletion <strong>of</strong>802.16e service flows. The SFM manages local resource in<strong>for</strong>mation and per<strong>for</strong>ms the admissioncontrol (AC) function, which decides whether a new service flow can be admitted into thenetwork.Service flow authorization. The SFA is a logical entity in the ASN. A user QoS pr<strong>of</strong>ile maybe downloaded into the SFA during network entry. If this happens, the SFA evaluates the incomingservice request against the user QoS pr<strong>of</strong>ile and decides whether to allow the flow. If the userQoS pr<strong>of</strong>ile is not with the SFA, it simply <strong>for</strong>wards the service flow request to the PF <strong>for</strong> decisionmaking. For each MS, one SFA is assigned as the anchor SFA <strong>for</strong> a given session and is responsible<strong>for</strong> communication with PF. Additional SFAs may exist in an NAP that relays QoS-relatedprimitives and applies QoS policy <strong>for</strong> that MS. The relay SFA that directly communicates with

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

Saved successfully!

Ooh no, something went wrong!