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.
user<br />
access<br />
device<br />
106<br />
sound/speech<br />
video/image<br />
data<br />
mobile<br />
specific<br />
telephony Hifi-sound/-program<br />
teleaction ISDN<br />
video-telephony/-conference<br />
message file transfer<br />
location/navigation<br />
telefax<br />
inter-PABX/-LAN<br />
1 10 100<br />
kbit/s<br />
1000<br />
Figure 3 Some services that might be supported in a TGMS<br />
terminal<br />
mobile<br />
station<br />
mobile<br />
termination<br />
Figure 4 Functionality in mobile<br />
communications systems<br />
base<br />
station<br />
tranceiver<br />
A base station system can be composed<br />
of a transceiver and a controller. A<br />
transceiver consists of the transmitter and<br />
the receiver units for (de-)multiplexing,<br />
frequency conversion, channel (de-)coding,<br />
etc. A number of transceivers could<br />
be controlled by a base station controller<br />
that may perform channel allocation,<br />
some cryptographic procedures, etc. A<br />
switching function is normally a necessity<br />
in any larger system. Control and<br />
data functions are required for handling<br />
the mobility, the services and the storage<br />
of related information. Following the<br />
architecture of an Intelligent Network<br />
(IN) special resources could also be defined<br />
implementing voice mail, answering<br />
machines, etc.<br />
Even though the functional entities are<br />
depicted as separate units, the physical<br />
implementation may vary, e.g. by connecting<br />
the elements with a MAN<br />
(Metropolitan Area Network), ref. e.g.<br />
[5], [9].<br />
base station<br />
system<br />
base station<br />
controller<br />
data<br />
base<br />
control<br />
The section where mobile networks differ<br />
most from other networks is naturally<br />
the air interface, i.e. between the mobile<br />
stations and the base stations, together<br />
with the corresponding functional units.<br />
For the other sections, we will find tasks<br />
similar to those valid for most telecommunications<br />
systems. These include both<br />
the handling of user connections and the<br />
signalling. However, specific considerations<br />
due to the mobile nature of the<br />
users/terminals must be included.<br />
An additional aspect is that several operators/providers<br />
may be involved, requiring<br />
mechanisms for mutual recognition<br />
of identities and rights.<br />
As we find a high level of resemblance<br />
between the wireless and fixed systems,<br />
the reuse of functions and the integration<br />
are topics of special interest. For integrating<br />
a mobile system and a fixed network,<br />
a number of integration levels can be<br />
defined, e.g.:<br />
- service<br />
- signalling<br />
- functional.<br />
Here, integration means common use of<br />
the relevant elements. For instance, by<br />
special<br />
recources<br />
signalling integration the signalling messages<br />
and the procedures are capable of<br />
dealing with the requirements from each<br />
of the systems (mobile and fixed terminals).<br />
Two extreme integration schemes can be<br />
described: firstly as a stand-alone solution<br />
and secondly as a completely integrated<br />
solution. The first case could be<br />
requested to ease the introduction of<br />
mobile systems. The latter solution could<br />
be the most economic one according to<br />
the scope considerations. However, some<br />
enhancements of capabilities in the fixed<br />
network may be needed for the fully integrated<br />
solution, e.g. to allow for unrestricted<br />
handovers between the various<br />
application areas.<br />
The integration solution also has impact<br />
on the performance studies of these systems.<br />
If the equipment examined is used<br />
for handling a number of services,<br />
the load impact from these<br />
services should be included in the<br />
study. Most likely, this would<br />
increase the dimensionality of<br />
the problem, at least before<br />
applying techniques for reducing the<br />
dimension.<br />
3.2 Layers<br />
In each of the sections described in the<br />
previous part, a number of protocols can<br />
be applied, depending on the integration<br />
scheme chosen. For each of the protocols<br />
certain aspects could be studied. Some<br />
protocol stacks, as defined in international<br />
standardisation organisations, are usually<br />
elaborated. The number of layers<br />
defined will depend on the configuration,<br />
e.g. a single link, a network, and the efficiency<br />
to be achieved, e.g. to avoid some<br />
of the overhead information. In addition,<br />
each top level protocol can be aimed for<br />
controlling a few of the aspects relevant<br />
for the system. For instance, one relationship<br />
can be defined between the base<br />
station controller and the mobile control<br />
function, while another is defined between<br />
the mobile station and the control<br />
function. Naturally, these would have<br />
different purposes. When the performance<br />
of a link with related protocol processors<br />
are examined, the characteristics<br />
of each of the protocols could have an<br />
impact on the resulting performance<br />
measures.<br />
In the physical layer (according to the<br />
protocol stack) several of the mechanisms<br />
present will influence the resulting<br />
quality of a connection. Some of these<br />
mechanisms are: