Returns the route for the SNC. 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.
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 NMS specifies if it wants to retrieve only resources in the layer of the SNC (the cross-connections that belong to the SNC), or higher order cross-connections also (the cross-connections of other SNCs that are used to carry the traffic of the queried SNC).
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 an SNC.
This operation also works for bundled SNCs. In the case of a bundled SNC, the EMS returns a set of cross connections betweens GTPs.
In case of an SNC that represents a trail (to be identified by the roles of its end points) the operation getRouteAndTopologicalLinks() shall be used to facilitate the delivery of the TLs that support the trail termination inclusions of the SNC.

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when an EMS does not implement the specified includeHigherOrderCCs value.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
