CC
Host
Host
(CC-Access)
Host
(Gateway Core)
Channel
(Network 1)
Channel
(Network 2)
Node_GW
Node_NW2Node_NW1
CC CC CC
Host
Host
(CC-Access)
Figure 2: Extended Model Structure for networked embed-
ded systems.
application is not yet designed. Therefore the hosts
realize the specific sublayers to access the CCs. The
Gateway Core can be seen as an application of the
node providing the gateway base function. This con-
cept fits the described modeling strategy. Anticipating
a more detailed model containing different applica-
tions in a node divided in several tasks it is possible
to extend this architecture to enable the analysis of the
system behavior including other effects, e.g. proper-
ties of task scheduling.
Gateway facilities handle the data exchange be-
tween heterogeneous computer networks. Normally,
they are designed to combine specified networks, and
fulfill specified needs, which are based on the appli-
cation. Hence, there is no predefined specification of
a gateway. Although there are no fixed design ap-
proaches for gateway design, certain common func-
tions can still be assumed for any specialized com-
munications gateway: routing, protocol conversion,
dataflow control, real time constraint checking for
message transmission and message filtering or seg-
mentation. The purpose of this paper is to develop
a universal gateway model, which facilitates the com-
munications between different networks. The design
of the presented approach is similar to the idea of a
time triggered gateway described in (Shaheen et al.,
2007).
As described in (Fahmy, 1995), the gateway
model is based on a shared medium approach, which
uses an internal network to exchange uncommitted
messages between Host and Gateway Core. Received
frames are converted to an uncommitted protocol, af-
ter which the information is handled by the gateway
module. Finally the information is converted to match
the destination protocol. The uncommitted protocol
contains three values: Source Identifier, Destination
Identifier and Datafield. The routing information of
each message can be identified by Source Identifier
and Destination Identifier. The data of the received
message is stored in the Datafield of the uncommit-
ted message. To fulfill the flexibility requirement the
gateway model is a composition of two kinds of mod-
ules: protocol related and unrelated modules. Only
uncommitted gateway messages can be processed in-
side the protocol unrelated modules, and the proto-
col related modules process the specific protocol mes-
sages. In order to extend the gateway model to sup-
port a larger amount of protocols, only the protocol
related modules need to be created, while the proto-
col unrelated modules remain unchanged. This ap-
proach provides enormous reusability, replace ability
and extensibility. It allows an easy generation of a
customized gateway to realize relevant system char-
acteristics.
An important aspect of the gateway functionality
refers to (H¨orner, 2007). A gateway should provide
at least two methods of data exchange - PDU based
and signal based gateway functions. A PDU gate-
way routes the protocol data units (PDUs) unchanged
between two networks. In this case the data carried
on both networks, source and destination, are identi-
cal regarding content and length. It is also possible,
that only signals, which are contained in the received
PDUs from source network, are needed on the other
network. In this case, the gateway does not trans-
fer the entire PDU, but sends the individual signals
to the corresponding destination network. To achieve
this, a single received PDU is disassembled in signals
according to the specification of the source network.
Afterwards signals are grouped together congruent to
configuration of the destination network and assem-
bled to PDUs, which are send across the destination
network.
The central unit of the gateway model is the mod-
ule Gateway Core shown in Figure 3. This module
contains protocol unrelated functions, e.g. buffering
of received messages, routing, message segmentation
and disassembling messages into signals. Based on
the specification of function blocks with standardized
interfaces a high adaptability of the architecture is
achieved allowing the extension and substitution of
single functions. Therefore it is possible to analyze
the system performance of several realizations differ-
ing in their buffer strategy. In contrast to the gateway
TransmitMessage
TransmitSignal
SplitFrameToSignal
SendMsg
RoutingUnitDelay
Delay
FIFOQueue
CoreControlUnit
CoreSwitch
Init_Gateway
Trigger
FromHost CtrlMsgInput
OverFlow
ToHost
Figure 3: Module Gateway Core.
core, the protocol related gateway functions, such as
protocol conversion, initialization of the communica-
ICINCO 2009 - 6th International Conference on Informatics in Control, Automation and Robotics
232