20.11.2012 Views

Contents Telektronikk - Telenor

Contents Telektronikk - Telenor

Contents Telektronikk - Telenor

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

vision of suitable information on 1) the<br />

service as actually provided, 2) the QoS<br />

as actually provided, and 3) the cost<br />

incurred as related to the service and<br />

QoS. Concerning QoS characteristics, the<br />

following generic QoS characteristics are<br />

defined:<br />

- Time delay represents the difference in<br />

time between two related events. The<br />

time delay characteristic is quantified<br />

in any units of time such as seconds,<br />

milliseconds, etc.<br />

- Time variability represents the variability<br />

of a time or a time period. It<br />

relates to the dispersion or jitter that<br />

can be tolerated when time periods are<br />

involved.<br />

- Time window represents specific<br />

period of time. It is a bounded time<br />

interval which is defined by a starting<br />

time and a time delay, by a starting and<br />

an end time or by a time delay and an<br />

end time.<br />

- Capacity represents the amount of service<br />

that can be provided in a specified<br />

period of time.<br />

- Accuracy represents the correctness of<br />

an event, a set of events or a condition.<br />

Accuracy is a QoS characteristic of<br />

concern to the user, for whom this<br />

characteristic refers to the user information<br />

only.<br />

- Protection represents the security<br />

afforded to a resource or to information.<br />

Protection is quantified as a probability<br />

of failure of the protection.<br />

- Cost represents a means of assigning<br />

value to an object. Cost is measured in<br />

terms of currency/unit.<br />

- Priority represents the importance of<br />

an object or the urgency assigned to an<br />

event.<br />

- Availability represents the proportion<br />

of time when satisfactory service is<br />

available.<br />

- Reliability represents the probability<br />

that accuracy will remain above a defined<br />

requirement (i.e. that failures will<br />

not occur).<br />

- Coherence is the QoS characteristic<br />

that represents the degree of correlation<br />

between two or more objects<br />

(events, actions or information).<br />

3.2 The model of QoS<br />

The purpose of the model of QoS for OSI<br />

is to define the basic concepts necessary<br />

for the description of QoS as it applies to<br />

(N)-QoSrequirements<br />

(1)<br />

(N)-service-user<br />

(N)-QoSrequirements<br />

(4)<br />

open systems. Figure 3.2 illustrates the<br />

external flow of QoS requirements in a<br />

confirmed (N)-service-facility. The<br />

model of QoS recognises two types of<br />

entities performing functions related to<br />

the operation and management of QoS:<br />

- layer QoS entities<br />

- system QoS entities.<br />

This is the same classification as used in<br />

the ISO recommendations for specification<br />

of OSI Management in the Recommendations<br />

ISO 9595-96, 10165:1-4 and<br />

10040. Layer QoS entities are associated<br />

with the operation of a particular (N)subsystem,<br />

and system QoS entities have<br />

a system-wide role.<br />

The layer QoS entities comprise: the (N)service<br />

user, the (N)-policy-control-function<br />

((N)-PCF), the (N)-QoS-control<br />

function ((N)-QCF), the (N)-protocolentity<br />

((N)-PE) and the (N-1)-serviceprovider.<br />

Figure 3.3 illustrates the total<br />

flow related to outgoing (N)-QoS-requirements.<br />

The (N)-PCF receives the<br />

(N)-QoS requirements submitted by the<br />

(N)-service-user and applies specific<br />

policies defined for the (N)-subsystem.<br />

Examples are policies related to time<br />

(N)-QoSrequirements<br />

(3)<br />

(N)-service-provider<br />

(N)-service-user<br />

(N)-QoSrequirements<br />

(2)<br />

Figure 3.2 Flow of QoS requirements in a confirmed (N)-service facility (from [27])<br />

(N)-QoSrequirements<br />

(N)-PCF<br />

(N)-QoSrequirements<br />

(N)-serviceprovider<br />

(N)-service-user<br />

(N)-QCF<br />

(N-1)-service-provider<br />

critical communications. (N)-QCF will<br />

decide if the QoS requirements can be<br />

met by the operation of an existing (N)-<br />

PE. If so, such an (N)-PE is selected, otherwise<br />

the call is rejected. The QoS<br />

requirements can be modified before<br />

sending them to the (N)-PE. The (N)-PE<br />

can also reject the received QoS requirements.<br />

In order to perform its function<br />

the (N)-QCF may also need to access<br />

information provided by the system QoS<br />

entities.<br />

The system QoS entities comprise: the<br />

system policy control function (SPCF),<br />

the system QoS control function (SQCF),<br />

the system management agent (SMA),<br />

the system management manager (SMM)<br />

and the resource manager (RM). These<br />

system entities are primarily concerned<br />

with management functions, and the set<br />

of system and layer QoS entities described<br />

constitutes a functional decomposition<br />

of an open system for the purpose of<br />

describing QoS management. In [27]<br />

some figures illustrating the relationship<br />

between the layer and system QoS entities<br />

are given. Figure 3.4 illustrates the<br />

relationship between the layer and the<br />

system entities.<br />

(N)-QoSrequirements<br />

Figure 3.3 Outgoing flow of QoS requirements (from [27])<br />

(N-1)-QoSrequirements<br />

(N)-PE<br />

QoS-related<br />

protocol<br />

elements<br />

59

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

Saved successfully!

Ooh no, something went wrong!