Operation void getRouteAndTopologicalLinks (Route route = NA, CIS SequenceOf TopologicalLink topologicalLinkList = NA), in Class SubnetworkConnection

Documentation
Like the operation getRoute, this operation returns the route, in terms of cross connections, for the SNC whose name is specified as a parameter. It also returns the list of topological links for that SNC that are used in the route.
If the SNC has more alternative routes, then it retrieves the intended route if the SNC is pending or partial, otherwise it retrieves the active route. This because there can be more partial routes and no active route, in such case the intended route is replied, as it is not known which of the partial routes is the candidate for becoming the active route.
The route information, in the form of cross connections, should identify the resources allocated to the SNC at the time of the request and the way in which these resources are used. For example, for a resilient SNC that is implemented in the subnetwork using subnetwork connection protection, all details of the route including normal and alternative paths should be provided. If the SNC is using some form of dynamic rerouting then it is clearly acceptable that the route include only the single thread of cross connections that is supporting the traffic (as there may be many alternative potential paths that could be selected).
The list of topological links can be used in conjunction with the cross connections to lay out the entire route through the subnetwork.
Unlike the operation getRoute, this operation always retrieves resources in all layers that support the route. This includes all cross connections of the SNC (i.e. the cross connections that are in the layer of the SNC) and all higher order cross connections (i.e. the cross connections of server SNCs that are used to carry the traffic of the queried SNC). It also includes all topological links (at any layer) that any traffic of the SNC passes across.
All cross connections allocated to the SNC must be returned, even if they are not active in the managed elements. This allows the NMS to query the route that will be used before activating the SNC.
This operation also applies to bundled SNCs.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when the EMS does not support this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.

Protocol |  | Qualification |
Exceptions |  | Size |
Time |  | Concurrency | Sequential
Export Control | PublicAccess |  |

Preconditions
None
Postconditions
No change in the system.
Semantics

Arguments

route
/* out */ The Route object represents the sequence of cross connections that comprise the working and protected (if applicable) route for the connection.
topologicalLinkList
/* out */ List of topological links that comprise the working and protected (if applicable) route for the connection.