Node Domain

Network models in Modeler are constructed from two broad classes of components: communication nodes and communication links. The internal structure of these objects, for the most part, is not visible at the network level. This section presents the methods used to specify the internal structure and therefore much of the capabilities of communication nodes. For more information about communication links, see Chapter 9 “Communication Mechanisms” on page 331.

Both the structural complexity of network nodes and their scope of activity can vary greatly depending on the system which is modeled. On the low end of complexity and function, simple terminals (connected to a host computer via serial connections) can be considered nodes of a star network. On the other end of the complexity spectrum, the network management center of a nationwide public packet network can also be considered as one hub node. The table below presents some typical examples of node models that can be built with Modeler.

Table 88: Typical Node Models

Node Type General Functions
Workstation Can generate and receive transfers of files or sparse packets and manage several concurrent network connections.
Packet Switch Supports large numbers of incoming and outgoing data links and performs packet routing at high speeds.
Satellite Terminal Generates and receives packets according to a channel access protocol. Acts as a multiplexor for many incoming links.
Remote Data Sensor Acts as a simple source of packets, usually transmitting them in bursts.

Because the goal of using Modeler is to construct executable simulation models of communication networks, internal node functions must be modeled sufficiently well that the overall simulation of network behavior is accurate. The system provided by Modeler is powerful enough to specify virtually any form of communication node. Moreover, it supports reusability of node substructures, and sharing of effort between various members of a design or development team.

Modeler’s node modeling system is based on a block-structured approach, which is familiar to most engineers and used extensively in modeling system architectures. Some examples of other applications which use this approach are signal processing, process control, and three-dimensional computer graphics. In these applications, the blocks operate respectively on analog or digital signals, fluids or other media, and polygons or vectors. Block-structuring is a natural technique for describing hardware systems, and can also be an effective tool when describing the relationships between high-level software objects with well defined interfaces. In fact, the International Standards Organization’s Open Systems Interconnect (OSI) Reference Architecture for data communications networks is based on a block-structured approach, where each block corresponds to a different protocol layer. Like the OSI architecture, the node models in Modeler contain blocks which operate on packets, so it is well suited to modeling protocol layers. This aspect of Modeler is described in Modeling Layered Protocols.

A node model is composed of a series of connected blocks called modules. Each module contains a set of inputs and outputs, some state memory, and a method for computing the module’s outputs from its inputs and its state memory. The manner in which this computation takes place depends upon the type of module. Some modules have predefined behavior to accomplish a specific purpose, while the behavior of other types of modules may be specified by the model designer.

Node models specify the manner in which the inputs and outputs of various modules are connected using objects called connections. There are two types of connections, one to carry data packets, and one to transmit individual values. A module can send data packets over its output packet streams, and receive them from its input packet streams. It may also send individual values over output statistics, and receive them from input statistics. The connection from a source module’s output stream to a destination module’s input stream is called a packet stream object. Likewise, the connection between a source module’s output statistic and a destination module’s input statistic is called a statistic wire object. (the connection objects are usually referred to as packet streams and statistic wires, or simply streams and statwires, respectively). Other more abstract intermodule communication mechanisms are available. For more details, see Chapter 9 “Communication Mechanisms” on page 331.

Modules represent the various functional areas of a node, whether implemented in hardware or software. In cases where portions of a node model correspond to hardware structures, separate modules may correspond to specific hardware subsystems that physically exchange data via parallel buses or serial data links. For software structures, modules may correspond to software layers (or sublayers) that pass packets via function calls or shared memory. In some cases, modules might have no physical counterparts in the real node, but may be used to set up specific test cases or be dedicated to computing specialized statistics.

The next two sections define the capabilities of the various types of modules and connections, and illustrate their specific uses within node models. The remaining sections describe the techniques used in creating specific types of models, including layered protocols, queues, and shared resources.

For more information see: