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.
Testing ATM switches<br />
BY SVEINUNG O GROVEN<br />
Abstract<br />
The telecommunications industry is<br />
presently witnessing the broadband<br />
integrated services digital network (B-<br />
ISDN) evolution. B-ISDN, and specifically<br />
asynchronous transfer mode<br />
(ATM) technology as the chosen solution<br />
by ITU-T, may be looked back<br />
upon in a few years as being elementary<br />
and simple. Today this is definitely<br />
not the case. Experience in traffic profiles<br />
in the various public B-ISDN network<br />
topologies is limited. With various<br />
equipment and private networks<br />
connected to the public network the<br />
complexity will increase many times.<br />
The question asked by many is what<br />
traffic profiles will the future telecommunications<br />
networks experience.<br />
Some of these foreseen traffical scenarios<br />
and the influence these will have on<br />
traffic profiles are presented.<br />
B-ISDN pilot projects are being carried<br />
out world-wide. Benchmark tests<br />
and performance evaluations are constantly<br />
being made. However likely or<br />
unlikely, various traffic models are<br />
suggested used in these tests. Thoughts<br />
around the validity of these tests are<br />
brought forward.<br />
In order to test the Ericsson ATM<br />
switch, traffical switch performance<br />
tests were carried out. The theory<br />
behind these tests are outlined. Finally,<br />
a comparison of theory and reality<br />
based on practical test experience is<br />
made.<br />
1 Introduction<br />
One of the main problems associated<br />
with the dimensioning and testing of<br />
ATM networks is the fact that the standards<br />
are not yet completed. Experience<br />
gathered through tests will aid the completion<br />
of these standards, and that is<br />
why these performance measurements,<br />
and many other quality of service (QoS)<br />
measurements, are so important. Of<br />
course, before performance measurements<br />
can be made, conformance and<br />
interoperability testing must be completed.<br />
Even these tests reveal inconsistencies<br />
and misunderstandings of the standards<br />
and equipment being developed.<br />
Figure 1 shows an example of a simple<br />
B-ISDN network. Even with such a<br />
simple network configuration the profiles<br />
of many different traffic sources are difficult<br />
to predict. Bearing in mind that this<br />
is an early configuration, measurements<br />
made today and the traffic profiles experienced<br />
at the measurement points of<br />
interest will be altered as the number of<br />
users, the amount of traffic, and the types<br />
of applications evolve.<br />
1.1 A simple network scenario<br />
Figure 1 gives a simplified view of a possible<br />
network scenario and some of the<br />
measurement points of interest.<br />
Network topologies are one of the main<br />
factors which will influence the traffic<br />
profiles seen at the measurement points<br />
of interest. For example, whether a user<br />
network interface (UNI) is connected to a<br />
local area network (LAN) or is used for a<br />
video on demand (VoD) distribution service<br />
is of a major consequence to the<br />
traffic profiles.<br />
Standardisation bodies estimate the performance<br />
objectives which should be<br />
provided by the network, but the end user<br />
and applications being run will determine<br />
the quality required.<br />
The main objective of the tests outlined<br />
in this article was to estimate the performance<br />
of the switch under test. Some<br />
tests needed to be repeated many times,<br />
requiring quick and simple test routines,<br />
while others were simplified due to limitations<br />
in the test equipment.<br />
Private<br />
Network<br />
Private<br />
Network<br />
Operator A<br />
UNI<br />
UNI<br />
ICI - Inter Carrier Interface<br />
NNI - Network Node Interface<br />
UNI - User Network Interface<br />
Public<br />
Network<br />
1.2 Broadband services<br />
Based on a basic knowledge of the wide<br />
range and variety of broadband services<br />
and applications being defined today, we<br />
realise that future applications may only<br />
be limited by our imagination. These<br />
may exhibit totally different traffic characteristics<br />
from those foreseen today.<br />
Bearing this in mind, we also realise the<br />
need to define reference points and standard<br />
test suites for performing QoS evaluations.<br />
In due time, experience will supply<br />
the information needed to dimension<br />
these networks properly.<br />
1.3 ATM traffic<br />
Various different traffic types have been<br />
specified to date. We have ATM traffic<br />
in its most simple form, Constant Bit<br />
Rate (CBR). The Cell Transfer Delay<br />
(CTD) and Cell Delay Variation (CDV)<br />
of CBR traffic is of course very low (typically<br />
some tens or a few hundreds of<br />
microseconds) and peak rate policing is<br />
an adequate mechanism for controlling<br />
this traffic. Variable Bit Rate (VBR) traffic<br />
may exhibit greater CTD and CDV<br />
(in the order of milliseconds) and will in<br />
addition require the use of a sustainable<br />
cell rate policing algorithm and a maximum<br />
burst tolerance. Two types of VBR<br />
traffics are defined; real-time and non<br />
NNI<br />
ICI<br />
Operator B<br />
Public<br />
Network<br />
ICI<br />
Public<br />
Network<br />
Figure 1 ATM broadband network and relevant performance measurement points<br />
ICI<br />
147