The operation creates a new SubnetworkConnection.
The SNC is created with its intended route, in locked state. By means of other operations it is possible to add (then remove) additional routes for restoration purposes. By means of additional info, it is possible to specify if the intended route is EXCLUSIVE or not; if EXCLUSIVE, then the EMS must find a route that does not conflict or share CCs or CTPs with any other existing routes of other SNCs, in any administrativeState.
Once an EXCLUSIVE (intended) route has been created by EMS, any further creation operation which conflicts with the exclusive route shall be refused.
The operation also applies to bundled SNCs.
At a CM end point the span of the SNC starts with a fixed or flexible connection through the ME at the SNC layer, i.e. the connectable layer of the end point. At an LC end point the span of the SNC starts with a G.805 link connection, i.e. connectivity which is adapted from (i.e., provided by) a server layer, e.g. from/by a topological link.

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when an EMS does not implement this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised when any input parameter is syntactically incorrect (e.g. an attribute of sncCreateData
    is invalid), or in case a bundled SNC is requested, the GTP endpoints of the SNC do not match, i.e., the GTPs
    do not have the same number of CTPs and in a particular order with respect to their layer rates or are not of the
    same layer rate.
4. ENTITY_NOT_FOUND - Raised when attribute values of SNCCreateData refer to an object that does not exist.
5. PROTECTION_EFFORT_NOT_MET - Raised when the NMS requests a SNC with a static protection level
    and protection effort that cannot be met by the EMS.
6. UNABLE_TO_COMPLY - Raised when the EMS is unable to find an appropriate route for the SNC.
7. UNSUPPORTED_ROUTING_CONSTRAINTS - Raised when the EMS does not support the routing constraints specified.
8. USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is not met.
9. OBJECT_IN_USE - Raised when the intended route is in conflict with an "exclusive" route of another SNC.
