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.

Number of type<br />

2 connections<br />

140<br />

Feasible<br />

state<br />

for maximum cell delay is not so strict,<br />

but the requirement for maximum cell<br />

loss ratio is stronger than for telephony.<br />

To cope with such problem QoS classes<br />

(performance parameter classes) on the<br />

cell level could be introduced. Otherwise<br />

the network will have to be dimensioned<br />

for the strongest requirements.<br />

Some data services require large buffers.<br />

A service like telephony which is delay<br />

sensitive requires small buffers. Some<br />

kind of buffer management scheme will<br />

have to be implemented, possibly combined<br />

with the use of separate physical<br />

links in the network, to satisfy the needs<br />

of both these services in the same network.<br />

For a given buffer size the maximum link<br />

allocation that the CAC can permit is<br />

given by the cell loss requirements. This<br />

maximum link allocation determines the<br />

capacity of the physical link in terms of<br />

the amount of bandwidth that can be allocated<br />

to the virtual connections crossing<br />

that physical interface. This then has<br />

direct implication on the number of physical<br />

interfaces needed towards a specific<br />

destination (i.e. for the trunk group) to<br />

satisfy the bandwidth needs determined<br />

by the trunk group dimensioning.<br />

3 The use of QoS classes<br />

QoS classes may be introduced to cope<br />

with different requirements for maximum<br />

cell loss ratio and cell delay variation,<br />

Legal transition<br />

between states<br />

Number of type<br />

1 connections<br />

Figure 1 Reversible transition diagram and coordinate<br />

convex set of feasible states for an ATM link with 2 traffic<br />

types<br />

and may improve the utilisation of the<br />

network depending on the traffic mix. A<br />

way to achieve this is by use of the Cell<br />

Loss Priority (CLP) bit in the ATM header<br />

and some kind of buffer administration<br />

that gives priorities to cells depending on<br />

the value of the CLP bit. In this way we<br />

will have two QoS classes, for example<br />

with cell loss requirements of 10-9 for the<br />

class with highest priority and 10-7 for<br />

the class with the lowest priority.<br />

The priority bit can be introduced at the<br />

cell level so that cells belonging to the<br />

same connection can have different priorities.<br />

This has been suggested for video<br />

services, but it seems not so much discussed<br />

in standardisation bodies anymore.<br />

The priority bit can also be used at the<br />

connection level. This leads to a classification<br />

of connections into two QoS classes<br />

depending on their requirement for<br />

maximum cell loss ratio. It is still unclear<br />

how to use the CLP bit, and the first<br />

switched ATM networks will probably<br />

use other methods to distinguish between<br />

QoS classes because it is possible to offer<br />

more than two classes by using other<br />

means than the CLP bit. One way is to<br />

use for instance the VPI field combined<br />

with some kind of buffer administration.<br />

Another way is to use some signalling or<br />

management message in the set-up phase<br />

to be able to allocate the connections to<br />

dedicated ATM links for the different<br />

QoS classes or to enable buffer management<br />

procedures to discriminate between<br />

the different connections.<br />

Different ways of dividing connections<br />

into QoS classes have been proposed,<br />

and it seems that at least three such<br />

classes will be implemented in early<br />

switched ATM networks:<br />

- A QoS class with a requirement for<br />

low cell loss (e.g. max 10-9 ) and high<br />

CDV tolerance or no end-to-end requirement<br />

on CDV (data applications).<br />

- A QoS class with a more relaxed<br />

requirement for cell loss (e.g. max<br />

10-6 ) but with a low CDV tolerance<br />

(voice and interactive video).<br />

- A QoS class with unspecified values<br />

(‘best effort’ and ‘low cost’ services).<br />

The use of different links for the different<br />

classes is only of interest if the offered<br />

traffic is high enough to justify the reservation<br />

of ATM links for the different<br />

classes. Anyhow, QoS classes with different<br />

requirements for maximum cell<br />

loss will have impact on dimensioning<br />

dependent on the way it is implemented.<br />

If separate ATM links and buffers are<br />

used with possible common overflow<br />

links, we can dimension the amount of<br />

resources needed for each QoS class separately.<br />

In this case each connection<br />

belongs to one QoS class, and the<br />

requirement for maximum cell loss ratio<br />

has implications for the maximum utilisation<br />

of the ATM link, that is the maximum<br />

number of simultaneous connections<br />

on each link. The overflow links<br />

will have to be dimensioned for the class<br />

with the strongest requirements. If buffer<br />

administration is used, this implies that<br />

connections belonging to different QoS<br />

classes may share the same ATM link but<br />

experience different cell loss ratios. Calculation<br />

of the admissible loading of the<br />

links will then be more complicated and<br />

is a matter for future research.<br />

4 Dimensioning of trunk<br />

groups in a complete<br />

sharing environment<br />

The task of this chapter is the dimensioning<br />

of the transmission resources in terms<br />

of the number of ATM links needed or<br />

the total bandwidth needed between two<br />

network nodes. The set of ATM links<br />

between two nodes is termed a trunk<br />

group.<br />

In this chapter we will concentrate on the<br />

general methodology for the dimensioning<br />

of trunk groups. This methodology is<br />

based on mathematical models that<br />

approximate the statistical behaviour of<br />

the traffic in the network. Inputs to this<br />

problem are the services specified as traffic<br />

types with certain traffic parameters,<br />

the offered traffic and a connection<br />

blocking objective for each traffic type.<br />

We will be faced with the difficulty of<br />

having services with different connection<br />

blocking objectives or we have to provide<br />

some service protection method (or<br />

both). This problem will be treated in the<br />

next chapter. We may also be faced with<br />

the problem of having traffic components<br />

with different QoS objectives even on the<br />

ATM level (i.e. maximum cell loss ratio).<br />

This problem was discussed in chapter 2<br />

and will not be elaborated any further.<br />

The connection blocking objective is the<br />

connection blocking at the connection<br />

level for a trunk group, defined as the<br />

proportion of the offered connections that<br />

are blocked. The connection is blocked if<br />

the connection is not accepted by the<br />

CAC function for any of the ATM links<br />

in the trunk group. All blocked connec-

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

Saved successfully!

Ooh no, something went wrong!