Contents Telektronikk - Telenor
Contents Telektronikk - Telenor
Contents Telektronikk - Telenor
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
58<br />
QoS user<br />
Service<br />
catagories user<br />
QoS<br />
QoS characteristic<br />
Service<br />
provider<br />
Figure 3.1 QoS user categories, characteristics and parameters<br />
tecture focuses on how the QoS functionality<br />
is modelled. In the QoS architecture,<br />
QoS is the objective and the QoSservice<br />
is the solution. The service in the<br />
functional architecture is replaced by the<br />
QoS-service in the QoS architecture. The<br />
service parameters are replaced by the<br />
QoS parameters. An optimum traffic<br />
solution is related to the existence of an<br />
optimum QoS architecture, i.e. an architecture<br />
that gives the necessary possibilities<br />
without being too costly. In the B-<br />
ISDN standardisation, simplicity has<br />
been a strong requirement. Focus on simplicity,<br />
however, can lead to non-optimal<br />
solutions.<br />
2.3 Traffic-handling<br />
functionality<br />
The functionality for the allocation,<br />
administration and reallocation of trafficcarrying<br />
resources within the operational<br />
QoS architecture, is denoted as traffichandling<br />
functionality. The design objective<br />
for the telecommunication services<br />
providing system is the offering of<br />
the defined set of services with a defined<br />
QoS at a minimum cost. The QoS architecture<br />
and the traffic handling functionality<br />
are tools for reaching this objective.<br />
The B-ISDN classification [8] of traffichandling<br />
functionality is as follows:<br />
- traffic control: the set of actions taken<br />
by the network to avoid congested<br />
conditions<br />
- congestion control: the set of actions<br />
taken by the network to minimise the<br />
intensity, spread and duration of congestion.<br />
In networks “up to LAN”, the traffic control<br />
functionality was: switching, multiplexing,<br />
routing, access, priority control<br />
and ack-based flow-control. Traffic handling<br />
functionality for high capacity networks<br />
has been a topic for discussion for<br />
several years. The traditional ack-based<br />
stop-and-wait and sliding window flow<br />
QoS parameters<br />
QoS requirement parameters<br />
QoS data parameters<br />
control mechanisms are in the general<br />
case insufficient. With high-capacity networks<br />
came transport protocols with<br />
rate-based flow-control. In this case the<br />
number of information units over a predefined<br />
time period is controlled, rather<br />
than the number of outstanding acknowledgements.<br />
With B-ISDN came concepts such as:<br />
connection admission control (CAC),<br />
usage/network parameter control<br />
(UPC/NPC) and traffic shaping. CAC is<br />
the set of actions taking place during call<br />
set up in order to establish a traffic contract<br />
and a connection, UPC/NPC is the<br />
set of actions taken by the network to<br />
monitor and control traffic, and traffic<br />
shaping comprises modification of the<br />
traffic characteristics. Network resource<br />
management, priority control and feedback<br />
control are also defined as part of<br />
the B-ISDN traffic handling functionality.<br />
Network resource management is<br />
the allocation of resources in order to<br />
separate flows according to service characteristics<br />
and feedback controls are the<br />
set of actions taken by the network and<br />
by the users to regulate the traffic submitted<br />
on ATM connections according to<br />
the state of network elements.<br />
3 The ISO/OSI QoS framework<br />
The Basic Reference Model for Open<br />
Systems Interconnection (OSI) defined in<br />
ITU recommendations X.200 and<br />
ISO/IEC 7498-1 provides a description<br />
of a model and the activities necessary<br />
for systems to interwork using communication<br />
media. The ISO/IEC “Quality of<br />
Service Framework” [27] will be a supplement<br />
to the description of QoS contained<br />
in this Basic Reference Model. In<br />
addition to the definition of QoS-related<br />
concepts, it contains the definition of a<br />
model of QoS and the definition of QoS<br />
parameter semantics.<br />
The present version of the Quality of Service<br />
Framework still has holes. The document<br />
is formally and compactly written.<br />
The following presentation in the Sections<br />
3.1–3.4 will therefore focus on the<br />
basic contents of this document rather<br />
than details. Section 3.1 presents QoS<br />
user categories, characteristics and<br />
parameters, Section 3.2 QoS parameter<br />
semantics. Section 3.3 presents the model<br />
of QoS for OSI. Section 3.4 is not<br />
directly related to the Quality of Service<br />
Framework document, but discusses QoS<br />
in existing layer-specific OSI recommendations.<br />
3.1 QoS user categories, characteristics<br />
and parameters<br />
The concepts QoS user categories, QoS<br />
characteristics and QoS parameters are<br />
essential in the OSI QoS framework. The<br />
relationships between these concepts are<br />
illustrated in Figure 3.1.<br />
A QoS user category is defined as “a policy<br />
objective that leads to the identification<br />
of a set of QoS characteristics”. The<br />
basic idea is to identify various classes of<br />
users and to define the QoS requirements<br />
based on these classes. A QoS characteristic<br />
is defined as “a quantifiable aspect<br />
of QoS, which is defined independently<br />
of the means by which it is represented<br />
or controlled”. QoS characteristics are<br />
intended to be used to describe the actual<br />
behaviour of systems. A QoS parameter<br />
is defined “as a variable relating to one<br />
or more QoS characteristics, values of<br />
which are conveyed between objects as a<br />
part of a QoS mechanism”. QoS parameters<br />
are classified as QoS requirement<br />
parameters and QoS data parameters.<br />
QoS requirements are a statement of<br />
requirements for one or more QoS characteristics.<br />
The defined fundamental QoS user categories<br />
are: the secure, the safe, the time<br />
critical, the highly reliable, the easy to<br />
use, the extensible/flexible, the low cost<br />
and the QoS monitorable/testable/auditable<br />
user categories. Most of these categories<br />
are self-explanatory. The QoS<br />
monitorable/testable/auditable user category<br />
is related to the requirements for<br />
monitoring, testing and auditing of the<br />
QoS for the provided service. QoS auditability<br />
means that the service user must<br />
be able to obtain verifiable evidence of<br />
the QoS as actually provided and of the<br />
cost incurred as related to the service<br />
provided and to the quality of that service.<br />
The requirement for audit of the<br />
service provided may be met by the pro-