The NMS uses this operation to request the creation of a GTP. The NMS can either specify the list of CTPs comprising the GTP (the list is placed in the listOfTPs parameter) or, in the case of contiguous CTPs of the same layerRate, the NMS may list the first CTP (in the initialCTPname parameter) and the number of following CTPs (in the numberOfCTPs parameter). The NMS may also provide the EMS with the flexibility to decide the list of CTPs by using the gtpEffort parameter. In this flexible mode the EMS uses the listOfTPs parameter or the initialCTPname/ numberOfCTPs parameters to determine the total requested bandwidth but it may return a GTP (newGTP parameter) with a different set of CTPs than those indicated in the original createGTP request. Note that this mode allows for the GTP components to be instantiated at a later time by the ME (e.g., upon detection of user's signal). Therefore the operation may successfully return a newGTP with an empty listOfTPs attribute (to be updated at a later time once the component CTPs are created in the ME).

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when EMS does not support GTPs.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. UNABLE_TO_COMPLY - Raised when the EMS cannot reply to the GTP creation request.
4. INVALID_INPUT - Raised when the GTP creation data is not well formed.
5. OBJECT_IN_USE - Raised when a CTP (to be associated to the GTP) is being used in a SNC, or is already associated
    to another GTP.
6. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents creating the GTP.
