Clarification regarding the LTP uuid formats received from MWDI application for the service /core-model-1-4:network-control-domain=cache/link={uuid}

[PrathibaJee]

Kindly please clarify our following doubt, In MWDI , all the LTP uuids will be prefixed by the mountName of the device. When we retrieve the link information from MWDI::/core-model-1-4:network-control-domain=cache/link={uuid} , Whether the logical-termination-point , retrieved in the below response will be in the format “mount-name” + “uuid of the ltp” (or) It will only consists of the uuid of the ltp as in live.

"end-point-list": [
        {
          "control-construct": "string", 
          "logical-termination-point": "string", 
          "layer-protocol": "string"
        }
        …
      ]

Reason for this ask is , as a consequent of this request , AIPS have to interact with MicroWaveDeviceGatekeeper to switchON/OFF the transmitter-power. So , if the response from MWDI responds uuid in the format , “mount-name” + “uuid of the ltp” , then while sending a request to the MWDG , we shall include a logic to remove the prefix(Mountname+) from the uuid.

[PrathibaJee]

In the MWDG application , the mountname present in the LTP uuid will be trimmed before processing the request as per the description provided for the uuid path Parameter in the MicroWaveDeviceGatekeeper application,

- name: uuid
                  in: path
                  required: true
                  schema:
                    type: string
                    example: 'LTP-MWPS-TTP-1-1'
                  description: >
+                   'The UUID of the LogicalTerminationPoint that is addressed by the request
+                  from {$request.parameters#uuid}.slice(10) for removing mountName and "+" '

So , AIPS dont have to remove the mount name from the LTPuuid, MWDG will take care of this. Hence closing this issue. Thanks.