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.
procedure is followed for subscribers on<br />
the lower.<br />
3.3.1 Normal configurations<br />
Traffic limits for the normal trunk configurations,<br />
which are the two link and<br />
four link configurations, are as follows:<br />
Two DTRH PBAs: 43.0 E<br />
Two DTRF PBAs: 82.5 E<br />
In the case of two DTRH PBAs the MD<br />
links are the bottleneck, i.e. Erlang’s formula<br />
for 58 channels is used. In the case<br />
of two DTRF PBAs the direct and crossover<br />
cluster link in the IRIM are the<br />
bottleneck, i.e. Erlang’s formula for 56<br />
channels multiplied by two is used.<br />
These limits are based on the use of the<br />
same trunk PBAs in the IRSUs in the<br />
MD, i.e. that all IRSUs have 2 DTRHs or<br />
2 DTRFs, respectively. If several IRSUs<br />
with DTRHs are connected to a DTRF in<br />
the IRIM, the DTRH PBAs should be<br />
distributed equally on the two MD links<br />
for capacity reasons.<br />
Furthermore, it is assumed that each<br />
IRSU has subscribers on both the upper<br />
and lower side of the system, i.e. at least<br />
two subscriber groups per IRSU. In an<br />
MD configuration, the total traffic from<br />
all IRSUs has to be within the above<br />
given limits.<br />
3.3.2 Special configurations<br />
If the traffic from the IRSUs is much<br />
smaller than 43.0 Erlang or a little more<br />
than 43.0 Erlang, some special configurations<br />
may be considered. These configurations<br />
are normally not recommended<br />
due to reliability reasons or traffic reasons<br />
(because of an asymmetric configuration).<br />
3.3.2.1 One trunk PBA configurations<br />
The economical one trunk PBA configuration<br />
can be used if the traffic is low and<br />
the reliability aspect is not considered<br />
that important.<br />
Figure 4 shows a one trunk PBA configuration<br />
with DTRF PBA in the IRIM and<br />
the IRSUs. The IRSUs have subscribers<br />
on both upper and lower side.<br />
Traffic limits for the one PBA configurations<br />
are as follows:<br />
One DTRH PBA: 18.2 E<br />
One DTRF PBA: 34.8 E<br />
In the case of DTRH PBA the MD link is<br />
the bottleneck, i.e. Erlang’s formula for<br />
29 channels is used. Very unbalanced<br />
traffic is well tolerated. For example there<br />
can be 17.0 Erlang from subscribers on<br />
the upper side and 1.2 Erlang from subscribers<br />
on the lower side and vice versa.<br />
In the case of DTRF PBA the bottleneck<br />
is the direct and cross-over cluster link in<br />
the IRIM, i.e. Erlang’s formula for 28<br />
channels multiplied by two is used. It<br />
must here be assumed that the traffic on<br />
the upper and lower is well balanced.<br />
If the trunk PBA in the IRIM or the trunk<br />
PBA in the IRSU fails, the connection<br />
between the IRIM and the IRSU will be<br />
disrupted, whereas for a normal configuration<br />
the traffic will use the alternative<br />
cross-over link when the direct link is<br />
disrupted.<br />
3.3.3 Asymmetric configuration<br />
This configuration has one DTRF PBA<br />
and one DTRH PBA in the IRIM and in<br />
the IRSU as well, i.e. three MD links.<br />
Figure 5 shows an asymmetric configuration.<br />
The asymmetric configuration may seem<br />
a good solution for traffic needs between<br />
the traffic capacity for a configuration<br />
with two DTRHs and two DTRFs in the<br />
IRIM. But it should only be used with the<br />
alternative channel allocation algorithm<br />
which chooses the MD link pair with<br />
most free channels.<br />
Without this alternative channel allocation<br />
algorithm the capacity can be improved<br />
by placing more subscribers on<br />
the side (upper or lower) where the<br />
DTRH is placed, which at first may seem<br />
surprising. When the traffic on the<br />
DTRH side is twice the traffic on the<br />
DTRF side the traffic capacity is 61<br />
Figure 4 Figure 5 Figure 6<br />
Erlang. In this case the high traffic from<br />
the DTRH will be blocked on the cluster<br />
link, but different from the opposite traffic<br />
situation the overflow traffic together<br />
with the direct traffic will now have two<br />
MD links available on the DTRF side.<br />
There will be very little overflow traffic<br />
from the DTRF side to the DTRH side.<br />
The point is to distribute the traffic so<br />
that the cluster links carry equal traffic as<br />
much as possible.<br />
If the alternative channel allocation algorithm<br />
is used the performance of the balanced<br />
upper and lower traffic case is<br />
improved. This algorithm has the effect<br />
of distributing the traffic more evenly<br />
and thus reducing the more bursty overflow<br />
traffic. With balanced traffic on the<br />
upper and lower side the traffic capacity<br />
is 66.3 Erlang and is dimensioned according<br />
to Erlangs formulae with 87<br />
channels minus PS channels. So, if this<br />
alternative channel allocation algorithm<br />
is used the asymmetric configuration<br />
may be considered.<br />
3.4 Mini IRSU<br />
The mini IRSU is an inexpensive, simple<br />
IRSU. The mini IRSU is special in two<br />
respects. It contains only one subscriber<br />
group and it has only one trunk PBA<br />
(DTRH or DTRF) which means it has no<br />
cross-over link. This means that a mini<br />
IRSU subscriber is a ‘worst case’ subscriber<br />
when the mini IRSU is in an MD<br />
with other non mini IRSUs. To fulfil the<br />
GOS requirement for all subscribers in<br />
an MD it is necessary to decrease the<br />
total traffic if the mini IRSU traffic increases.<br />
The traffic capacity for the mini<br />
IRSU is 17.4 Erlang. The bottleneck is<br />
the cluster link, hence Erlang’s formula<br />
with 28 channels is used. However, the<br />
bottleneck is quickly changed to the MD<br />
link with 29 channels when other non<br />
mini IRSUs are connected to the same<br />
MD and there are DTRHs in the IRIM. If<br />
there are DTRFs in the IRIM the bottleneck<br />
is again the cluster link.<br />
Figure 6 shows a configuration with<br />
DTRH PBAs in the IRIM and the IRSUs<br />
91