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.

previous drops in the MD and from the<br />

IRIM (incoming traffic).<br />

There are assumed n M/M/1 queuing systems<br />

(Markovian input process, Markovian<br />

service time distribution, one server)<br />

with first in first out (FIFO) queue discipline<br />

per PS channel where n is the number<br />

of PS channels. The n channels serve<br />

the whole MD.<br />

The server time is assumed to be proportional<br />

to the packet length with a service<br />

speed of 64 kbit/s. Two traffic models<br />

are given for the PS traffic, the medium<br />

traffic and the high traffic model. The<br />

medium and high traffic model has 10<br />

and 50 call attempts per hour (CAPH)<br />

per subscriber respectively. Each call has<br />

an average of 18 packets with an average<br />

length of 125 bytes. Since both outgoing<br />

and incoming PS calls are queued successively<br />

in all IRSUs and the IRSUs are<br />

considered as one common queue, all<br />

calls are considered outgoing.<br />

The maximum number of ISDN subscribers<br />

in an MD is 512. The results in<br />

the following sections are based on this<br />

number of subscribers. It is important to<br />

note that the tables reflect the total PS<br />

traffic equivalent to 512 subscribers and<br />

that realistic PS traffic will be much<br />

lower due to fewer ISDN subscribers in<br />

an MD.<br />

3.5.3 Results<br />

In the following text and tables the following<br />

abbreviations occur:<br />

λ: Packet arrival rate per second<br />

for a MD<br />

µ: Service rate in packets per<br />

channel<br />

CH: Number of PS channels<br />

CHT: Call Holding Time<br />

CAPH: Call Attempts Per Hour<br />

DELq: Average delay in milliseconds<br />

(ms) for a delayed<br />

packet<br />

DELall: Average delay in ms for all<br />

packets<br />

Qbyte: Average number of queued<br />

bytes per channel<br />

Load: Load per channel<br />

95%_all: Delay in ms for which 95 %<br />

of all packets are below<br />

95%_del: Delay in ms for which 95 %<br />

of the delayed packets are<br />

below.<br />

From Table 1 can be seen that for<br />

medium PS traffic one or two packet<br />

channels are sufficient. For high PS traffic<br />

three or four channels are sufficient,<br />

but one or two channels is impossible<br />

since the load is 2.0 and 1.0 respectively<br />

(a load higher than 1.0 gives an infinite<br />

queue).<br />

The delays depend on the packet length<br />

given the same load. In Table 2 the bytes<br />

per packet and packets per call are interchanged<br />

so that there are many short<br />

packets instead of few long packets.<br />

Short packets reduce the delays and average<br />

queue lengths. Since an objective is<br />

to minimise the number of long delays to<br />

avoid retransmission, shorter packets<br />

may be used.<br />

3.5.4 PS traffic in the signalling<br />

channel<br />

The PS traffic intensity generated by<br />

ISDN subscribers may be so small that<br />

an allocation of one separate PS channel,<br />

and hence a reduction in CS traffic<br />

capacity, would be an unsatisfactory utilisation<br />

of the system. Thus, the signalling<br />

(S) channel may be used as a combined<br />

channel for PS traffic and S traffic. This<br />

solution utilises the spare capacity of the<br />

S channel for PS traffic.<br />

The same queuing model as in the section<br />

‘Analytical model’ has been used.<br />

The abbreviation Wpacket is used for the<br />

weighted average packet length in bytes<br />

based on the distribution of CS and PS<br />

packets.<br />

The ‘2 CH’ and ‘4 CH’ columns in the<br />

tables correspond to a DTRH and a<br />

DTRF configuration respectively.<br />

CAPH and CHT is based on 0.08 Erlang<br />

per subscriber.<br />

CSpackets/call is 88 packets on an average,<br />

i.e. 88 S packets per CS call. CSbytes/packet<br />

is 33 bytes on an average.<br />

This assumes that all traffic carried in the<br />

MD originates and terminates here,<br />

which is a worst case. Approximately 2/3<br />

signalling is for the originating side. 1/3<br />

is for incoming traffic. Since only few<br />

calls use maximal signalling and the rest<br />

is balanced, the theoretical results should<br />

be slightly conservative.<br />

In Table 3 only S traffic is considered.<br />

The results in Table 3 clearly show that<br />

even with high S traffic the load contribution<br />

due to S traffic will be modest<br />

(worst case load-DTRH = 24.8 %). The<br />

average waiting time for all packets will<br />

not exceed 1.35 ms, and 95 % of the<br />

Table 1 PS Traffic<br />

CAPH/SUB 10 50<br />

Bytes/packet 125 125<br />

Packets/call 18 18<br />

λ 25.6 128.0<br />

µ 64 64<br />

1 CH 2 CH 3 CH 4 CH<br />

λ 25.6 12.8 42.7 32.0<br />

Load 0.40 0.20 0.67 0.50<br />

DELq 26.0 19.5 46.9 31.3<br />

DELall 10.4 3.9 31.3 15.6<br />

Qbyte 33.3 6.3 166.7 62.5<br />

95%_del 78 59 140 94<br />

95 %_all 54 27 121 72<br />

Table 2 PS Traffic<br />

CAPH/SUB 10 50<br />

Bytes/packet 18 18<br />

Packets/call 125 125<br />

µ 444 444<br />

1 CH 2 CH 3 CH 4 CH<br />

λ 177.8 88.9 296.3 222.2<br />

Load 0.40 0.20 0.67 0.50<br />

DELq 3.8 2.8 6.8 4.5<br />

DELall 1.5 0.6 4.5 2.2<br />

Qbyte 4.8 0.9 24.0 9.0<br />

95%_del 11 8 20 14<br />

95%_all 8 4 18 10<br />

Table 3 Signalling Traffic<br />

CAPH/SUB 3.2 9.6<br />

cht 90 30<br />

Bytes/packet 33 33<br />

Packets/call 88 88<br />

λ 40.04 120.16<br />

µ 242.42 242.42<br />

2 CH 4 CH 2 CH 4 CH<br />

Load 0.082 0.041 0.248 0.124<br />

DELq 4.4 4.3 5.4 4.7<br />

DELall 0.37 0.18 1.35 0.50<br />

Qbyte 0.25 0.06 2.69 0.58<br />

95%_del 13 12 16 14<br />

93

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

Saved successfully!

Ooh no, something went wrong!