Академический Документы
Профессиональный Документы
Культура Документы
Custom Search
etutorials.org/…/11.5+Dynamic+Servi… 1/5
2010/9/6 11.5 Dynamic Service Addition and Ch…
existing service flow. This is illustrated in Figure
11.15.
Image from book
etutorials.org/…/11.5+Dynamic+Servi… 2/5
2010/9/6 11.5 Dynamic Service Addition and Ch…
charac teristics, CS specific parameters and
sc heduling requirements. These parameters are:
CID:specifies the CID assigned by the BS to a
service flow. The CID is used in bandwidth requests
and in MAC PDU headers.
SFID: the primary reference of a service flow. Only
the BS may issue an SFID in BS-initiat ed DSA-
REQ/DSC-REQ messages and in its DSA-RSP/DSC-
RSP to SS-initiated DSA-REQ/DSC-REQ messages.
The SS specifies the SFID of a servic e flow using
this parameter in a DSC-REQ message.
Service class name: see Section 11.5.1 above.
QoS parameter set type: provisioned, admitted or
ac tive.
Traffic priority. The value of this parameter specifies
the priority assigned to a service flow. Given two
service flows identical in all QoS parameters besides
priority, the higher priority service flow should be
given lower delay and higher buffering preference.
For nonidentical service flows, the priority parameter
should not take prec edence over any conflicting
service flow QoS parameter. No specific algorithm for
using this parameter is given in the st andard. For
uplink service flows, the BS uses this parameter
when determining precedence in request service and
grant generation.
Scheduling service type. This is the one that should
be enabled for the associated service flow, between
the five defined sc heduling service types: BE
(default), nrtPS, rtPS, ertPS or UGS. If this
parameter is omitted, BE service is assumed. An
undefined sc heduling service type (implementation-
dependent) can also be set.
Other QoS parameters: maximum sust ained traffic
rate, maximum traffic burst, minimum reserved traffic
rate, minimum tolerable traffic rate, ARQ parameters
for ARQ-enabled connec tions, etc. (see QoS
parameters in Section 7.4).
Target SAID (Securit y Association IDentifier). This
indic ates the SAID on to which the service flow that
is being set up will be mapped. The SAID is a
security association identifier shared between the BS
and the SS (see Chapter 15).
CS specification. This specifies the CS that the
connection being set up will use. Possible choices
are No CS, Packet IPv4, Packet IPv6, Packet
802.3/Ethernet, Packet 802.1Q VLAN, Packet IPv4
over 802.3/Ethernet, Packet IPv6 over
802.3/Ethernet, Packet IPv4 over 802.1Q VLAN,
Packet IPv6 over 802.1Q VLAN and AT M.
11.5.3 Service Flow Modification and Deletion
Both provisioned and dynamically created service
flows are modified with the DSC message, which can
change the admitted and active QoS parameter sets
of the flow. A single DSC message exc hange can
modify the parameters of either one downlink service
flow or one uplink service flow.
A successful DSC transaction c hanges the service
flow QoS parameters by replac ing both the admitted
and ac tive QoS parameter sets. If the message
contains only the admitted set, the active set is set
to null and the flow is deac tivated. If the message
contains neither set, then both sets are set to null
and the flow is de-admitted. When the message
contains both QoS parameter sets, the admitted set
is checked first and, if the admission control
succ eeds, the ac tive set in the message is chec ked
against the admitted set in the message to ensure
that it is a subset. If all chec ks are successful, the
QoS parameter sets in the message bec ome the new
admitted and active QoS parameter sets for the
service flow. If either of the chec ks fails, the DSC
transaction fails and the service flow QoS parameter
sets are unchanged. Some service flow parameters,
including the service flow sc heduling t ype, may not
be c hanged with the DSC messages.
An SS wishing to delete a service flow generates the
DSD-REQuest message to the BS. The BS verifies
that the SS is really the service flow ‘owner’ and
then removes the service flow. The BS responds
using the DSD-RSP message. On the other hand, a
BS wishing to delete a dynamic servic e flow, no
longer needed, generates a delete request to the
associated SS using a DSD-REQuest. The SS
removes the service flow and generat es a response
using a DSD-RSP.
11.5.4 Authorisation Module
The authorisation module is a logical function within
the BS that approves or denies every change to QoS
parameters and c lassifiers associated with a service
flow. This includes every DSA-REQ message aiming
to c reate a new service flow and every DSC-REQ
message aiming to change a QoS parameter set of
an existing service flow. Such changes include
requesting an admission c ontrol decision (e.g. setting
the AdmittedQoSParamSet) and requesting
ac tivation of a servic e flow (e.g. sett ing the
ActiveQoSParamSet).
In the static authorisation model, the authorisation
etutorials.org/…/11.5+Dynamic+Servi… 3/5
2010/9/6 11.5 Dynamic Service Addition and Ch…
these provisioned service flows are permitted as long
as t he admitted QoS parameter set is a subset of
the provisioned QoS parameter set and the ac tive
QoS parameter set is a subset of the admitted QoS
parameter set. Requests to change the provisioned
QoS parameter set are refused. Requests to create
new dynamic service flows are refused. This defines
a st atic system where all possible services are
defined in the initial c onfiguration of eac h SS.
In the dynamic authorisation model, t he
authorisation module communicates through a
separate interfac e to an independent policy server.
This policy server may provide the authorisation
module with advance notice of upcoming admission
and ac tivation requests, and it specifies the proper
authorisation action to be taken on those requests.
Admission and ac tivation requests from an SS are
then chec ked by the authorisation module to ensure
that the ActiveQoSParamSet being requested is a
subset of the set provided by the policy server.
Admission and ac tivation requests from an SS that
are signalled in advance by the external policy server
are permitted. Admission and ac tivation requests
from an SS that are not presignalled by the external
polic y server may result in a real-time query to the
polic y server or may be refused.
Prior to the initial connec tion setup, t he BS retrieves
the provisioned QoS set for an SS. This is handed to
the authorisation module within the BS. The BS
cac hes the provisioned QoS parameter set and uses
this information to authorise dynamic flows that are
a subset of the provisioned QoS parameter set. The
standard states that the BS should implement
mec hanisms for overriding this automated approval
proc ess (such as described in the dynamic
authorisation model). For example it c ould:
a. deny all requests whether or not they have been
pre- provisioned;
b. define an internal table with a richer policy
mec hanism but seeded by the provisioned QoS set;
c. refer all requests to an external policy server.
| More
Remember the name: eTutorials.org. Copyright eTutorials.org 2008-2010. All rights reserved.
etutorials.org/…/11.5+Dynamic+Servi… 4/5
2010/9/6 11.5 Dynamic Service Addition and Ch…
etutorials.org/…/11.5+Dynamic+Servi… 5/5