signal route (Z.100)
<signal route definition area> ::=
<signal route symbol>
is associated with {<signal route name>
{[ <channel identifiers> | <external signal route identifiers> |
<gate> }
<signal list area> [ <signal list area>] }set }
is connected to
{{<process area> | <service area>}
{<process area> | <service area> | <frame symbol>} }set
<signal route symbol> ::=
<signal route symbol 1> | <signal route symbol 2>
A signal route symbol includes an arrowhead at one end (one direction) or one arrowhead at each end (bidirectional) to show the direction of the flow of signals.
For each arrowhead on the <signal route symbol>, there must be a <signal list area>. A <signal list area> must be unambiguously close enough to the arrowhead to which it is associated.
When the <signal route symbol> is connected to a <frame symbol>, for a <block type diagram>, then the <gate> it is associated with, is a gate defined for that block type by means of a <gate> or <graphical gate constraint> associated with the <block type diagram>. When the <signal route symbol> is connected to a <frame symbol>, for a <process type diagram>, then the <gate> it is associated with, is a gate defined for that process type by means of a <gate> or <graphical gate constraint> associated with the <process type diagram>.
A signal route represents a transportation route for signals. A signal route can be considered as one or two independent unidirectional signal route paths between two sets of process instances each denoted by a process definition, or between one set of process instances and the environment of the enclosing block, or between two services, or between a service and the environment of the enclosing process.
Signals conveyed by signal routes are delivered to the destination endpoint.
A signal route does not introduce any delay in conveying the signals.
When a signal instance is sent to an instance of the same process instance set, interpretation of the Output-node implies that the signal is put directly in the input port of the destination process.
Several signal routes may exist between the same two endpoints. The same signal type can be conveyed on different signal routes.
If a <block definition> or <block type definition> contains <signal route definition>s, then the <valid input signal set> in a <process definition>, if any, need not contain signals in signal routes leading to the set of process instances.
If a <process type definition> or <process definition> contains services, the <valid input signal set> is derived as the union of the input signals in the gates (in case of a <process type definition>) or the signals in signal routes leading to the process (in case of a <process definition>), the input signals on signal routes leading to the services and the <valid input signal set>s for the services. This set is called implicit <valid input signal set>. If the <valid input signal set> of the process is specified explicitly, it must be a subset of the implicit <valid input signal set>.