20.11.2012 Views

Contents Telektronikk - Telenor

Contents Telektronikk - Telenor

Contents Telektronikk - Telenor

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2 Generic concepts<br />

2.1 Quality of service (QoS)<br />

A service is the behaviour of some functional<br />

capability provided by a service<br />

provider to a service user (Figure 2.1).<br />

The service is defined by service primitives,<br />

and these service primitives carry<br />

service parameters. Within the context of<br />

ISO/OSI, a service is related to a specific<br />

layer, and an (N)-service is the service<br />

offered to the (N+1)-layer. The (N)-service<br />

is the result of the functionality of<br />

the (N)-layer-entity and the (N-1)-service.<br />

An (N)-service is offered at an (N)service<br />

access point. ITU defines teleservices<br />

and bearer services. A teleservice<br />

is a service that the user gets from the<br />

user terminal, while a bearer service is a<br />

service offered at some interface between<br />

the user and the network. The ITU services<br />

represent OSI (N)-services at specific<br />

(N)-service access points.<br />

ISO/OSI defines Quality of service<br />

(QoS) as “a set of qualities related to the<br />

provision of an (N)-service, as perceived<br />

by an (N)-service-user”. QoS is defined<br />

by ITU as “the collective effect of service<br />

performance which determine the degree<br />

of satisfaction of the user of the service”.<br />

The relative frequency of specific events<br />

within a service is used as a QoS measure.<br />

These specific events are used as<br />

quality criteria for the proper service<br />

functioning.<br />

The ISO definitions are found within the<br />

OSI QoS Framework [27]. The ITU definitions<br />

are found in E.800 “Quality of<br />

Service and Dependability Vocabulary”<br />

[17] and in I.350 from the series of ISDN<br />

recommendations [22]. In addition to the<br />

service concept, ITU also has the concept<br />

of network performance (NP) defined as<br />

“the ability of a network or network portion<br />

to provide the functions related to<br />

communication between users”.<br />

The concept traffic performance is often<br />

used in relationship with or instead of<br />

QoS. QoS is directly related to the use of<br />

common traffic resources. Examples of<br />

traffic resources are: nodes, transmission<br />

capacity, transmission links, routes, logical<br />

channels, buffers, windows, and also<br />

processing resources such as CPUs,<br />

buses and interface-circuits within nodes<br />

and end-systems. So the quantitative<br />

measure of QoS is directly related to the<br />

utilisation of the resources involved in<br />

providing the service, i.e. the traffic on<br />

these resources. So, traffic performance<br />

and QoS are two strongly related concepts.<br />

A QoS service is here defined as the<br />

QoS-related aspects of a service relationship.<br />

While a service comprises the total<br />

functionality of some capability, the<br />

QoS-service only comprises the aspects<br />

of a service that have meaning for the<br />

definition of the QoS. The QoS-service<br />

defines the nature of the QoS parameters<br />

carried on the service primitives. The<br />

QoS-service is relevant between adjacent<br />

layers, but is also relevant for general<br />

client-server relationships.<br />

2.2 QoS architecture<br />

The functional architecture of a telecommunication<br />

service providing system is<br />

defined as the total set of functional elements<br />

and the dynamic relationship between<br />

these functional elements. This<br />

architecture has an operational and a<br />

management part. The operational architecture<br />

defines the primary functionality<br />

related to the real-time handling of a call,<br />

while the management architecture defines<br />

the additional functionality needed<br />

for the administration of this operational<br />

functionality.<br />

A QoS architecture is a view of a functional<br />

architecture, considering the traffic-resource-related<br />

aspects, i.e. the traffic<br />

resources and the functionality for the<br />

Functional architecture<br />

Management<br />

architecture<br />

QoS Architecture<br />

Management<br />

architecture<br />

Service<br />

relationship<br />

Operational<br />

architecture<br />

Operational<br />

architecture<br />

Service<br />

user<br />

Service<br />

provider<br />

• Service<br />

• QoS<br />

Service primitives,<br />

service parameters<br />

Figure 2.1 A generic service relationship<br />

administration of these resources. Faulthandling<br />

functionality will be a part of<br />

the QoS architecture. This because of the<br />

tight connection between fault-handling<br />

and traffic resources. A QoS architecture<br />

will also have an operational and a management<br />

part, denoted as the operational<br />

and management QoS architecture,<br />

respectively. The relationship between<br />

the functional architecture and the QoS<br />

architecture is illustrated in Figure 2.2.<br />

QoS is a characteristic of how well the<br />

service is performed. But a system must<br />

also have the ability to provide a certain<br />

QoS. This ability can depend very much<br />

on the system architecture and accordingly<br />

on the principles for the realisation<br />

of system functionality. The QoS archi-<br />

User<br />

Provider<br />

QoS View<br />

User<br />

Provider<br />

• Service<br />

• QoS<br />

Service primitives<br />

service parameters<br />

• Service<br />

• QoS<br />

Service primitives<br />

service parameters<br />

Figure 2.2 The relationship between the functional architecture and the QoS architecture<br />

57

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

Saved successfully!

Ooh no, something went wrong!