Association Directions
Associations have a direction related with them. These directions are specified by the following symbolic constants:
EtsC_Topo_Assoc_Dir_InEtsC_Topo_Assoc_Dir_OutEtsC_Topo_Assoc_Dir_ThroughEtsC_Topo_Assoc_Dir_In_GlobalEtsC_Topo_Assoc_Dir_Out_Global
The “In” and “Out” associations of an object include:
- Any objects in the same subnet directly connected to its input and output ports, respectively
- Any connections (links in the same subnet, paths, or demands) that begin or end at the object
The “In Global” and “Out Global” associations are similar to “In” and “Out”, but connected objects are included regardless of subnet.
“Through” associations always involve a path object.
- For a path, the associated objects are the site and links explicitly specified as defining the path (including the head and tail sites), plus any demands to which the path belongs.
- For a site or link, the associated paths are those that explicitly include it. Because links optionally can be included or ignored in some path definitions, they might or might not be listed as topological associations.
- For a demand, the associated paths are only those that explicitly belong to the demand.
Table 41 lists the types of objects that can be associated for each reference object type and association direction.
Table 41: Association Pairs
| Reference Object Type | In | In Global | Out | Out Global | Through |
|---|---|---|---|---|---|
| site (fixed subnet; fixed node) | site, link (same subnet) path |
site, link (any subnet) path |
site, link (same subnet) path |
site, link (any subnet) path |
path |
| link (bus; simplex and duplex pt-pt link) | site (same subnet) | site (any subnet) | site (same subnet) | site (any subnet) | path |
| path | site (head/tail) | site (head/tail) | site (head/tail) | site (head/tail) | all attached nodes/links, all demands flowing through |
| demand¹ | site (source) | site (source) | site (destination) | site (destination) | all paths used |
| tap | bus (same subnet) | bus (any subnet) | bus (same subnet) | bus (any subnet) | none |
| bus | tap (same subnet) | tap (any subnet) | tap (same subnet) | tap (any subnet) | none |
Note 1: Point demands might not have a source or destination (or both), and thus would not have the corresponding association.