File: Applications/i3/OverlayI3.ned
Container for I3 module and trigger table
Author: Antonio Zea
The following diagram shows usage relationships between modules, networks and channels. Unresolved module (and channel) types are missing from the diagram. Click here to see the full picture.
If a module type shows up more than once, that means it has been defined in more than one NED file.
I3 | Module for I3 servers |
TriggerTable | Simple module to display stored triggers. Author: Antonio Zea |
Name | Type | Description |
---|---|---|
debugOutput | bool |
Name | Direction | Description |
---|---|---|
from_udp | input | gate from the UDP layer |
from_lowerTier | input | gate from the lower tier |
from_upperTier | input | gate from the upper tier |
to_udp | output | gate to the UDP layer |
to_lowerTier | output | gate to the lower tier |
to_upperTier | output | gate to the upper tier |
Name | Type | Description |
---|---|---|
i3.debugOutput | bool | inherited from BaseApp |
i3.triggerTimeToLive | numeric | expiration time for triggers |
i3.serverPort | numeric | server port |
module OverlayI3 parameters: debugOutput: bool; gates: in: from_udp; // gate from the UDP layer in: from_lowerTier; // gate from the lower tier in: from_upperTier; // gate from the upper tier out: to_udp; // gate to the UDP layer out: to_lowerTier; // gate to the lower tier out: to_upperTier; // gate to the upper tier submodules: i3: I3; triggerTable: TriggerTable; display: "i=block/table"; connections nocheck: from_udp --> i3.from_udp; to_udp <-- i3.to_udp; from_lowerTier --> i3.from_lowerTier; to_lowerTier <-- i3.to_lowerTier; from_upperTier --> i3.from_upperTier; to_upperTier <-- i3.to_upperTier; endmodule