summary:Query multiple Application Mobility Service resources.
description:The GET method is to retrieve information about the registered Application Mobility Service. Upon success, the response contains entity body with the list of application mobility services that are present for the requestor.
description:The GET method is to retrieve information about the registered Application Mobility Service. Upon success, the response message content contains the list of application mobility services that are present for the requestor.
summary:Create an Application Mobility Service resource.
description:The POST method is used to create a new application mobility service for the service requester. Upon success, the response contains entity body of created application mobility service with the service ID.
description:The POST method is used to create a new application mobility service for the service requester. Upon success, the response message content contains created application mobility service with the service ID.
operationId:AppmobilityservicesPOST
tags:
-app_mobility_services
@@ -94,7 +94,7 @@ paths:
/app_mobility_services/{appMobilityServiceId}:
get:
summary:Read an Application Mobility Service resource.
description:The GET method is used to retrieve information about this individual application mobility service. Upon success, the response contains entity body with the data type describing the registered Application Mobility Service.
description:The GET method is used to retrieve information about this individual application mobility service. Upon success, the response message content contains the data type describing the registered Application Mobility Service.
summary:Update an individual Application Mobility Service resource.
description:The PUT method is used to update the existing individual application mobility service. PUT method in this case has "replace" semantics. Upon successful operation, the target resource is updated with new Data Type received within the message body of the PUT request.
description:The PUT method is used to update the existing individual application mobility service. PUT method in this case has "replace" semantics. Upon successful operation, the target resource is updated with new Data Type received within the message content of the PUT request.
description:Upon success, a response body containing data type describing the updated application mobility service.
description:Upon success, the returned response message content contains data type describing the updated application mobility service.
content:
application/json:
schema:
@@ -212,7 +212,7 @@ paths:
description:'Therequestisacknowledged.
Theresponsebodyshallbeempty.'
Theresponsemessagecontentshallbeempty.'
content:
application/json:
schema:
@@ -238,15 +238,15 @@ paths:
/subscriptions:
get:
summary:Retrieve information of multiple subscriptions to notifications of Application Mobility Service event.
description:The GET method is used to retrieve information about the subscriptions for this requestor. Upon success, the response contains entity body with the list of links to the subscriptions that are present for the requestor.
description:The GET method is used to retrieve information about the subscriptions for this requestor. Upon success, the response message content contains the list of links to the subscriptions that are present for the requestor.
description:Upon success, a response body containing the list of links to requestor's subscriptions is returned.
description:Upon success, the returned response message content contains the list of links to requestor's subscriptions.
content:
application/json:
schema:
@@ -268,12 +268,12 @@ paths:
$ref:'#/components/responses/429'
post:
summary:Subscribe to notifications of Application Mobility Service event.
description:The POST method is used to create a new subscription to Application Mobility Service notifications. Upon success, the response contains entity body describing the created subscription.
description:The POST method is used to create a new subscription to Application Mobility Service notifications. Upon success, the response message content contains description of the created subscription.
summary:Read information of subscription of Application Mobility Service.
description:The GET method is used to retrieve information about this subscription. Upon success, the response contains entity body with the data type describing the subscription.
description:The GET method is used to retrieve information about this subscription. Upon success, the response message content contains the data type describing the subscription.
summary:Update an individual subscription to notification of Application Mobility Service event.
description:The PUT method is used to update the existing individual subscription. PUT method in this case has "replace" semantics. Upon successful operation, the target resource is updated with new subscription parameters received within the message body of the PUT request.
description:The PUT method is used to update the existing individual subscription. PUT method in this case has "replace" semantics. Upon successful operation, the target resource is updated with new subscription parameters received within the message content of the PUT request.
summary:Read information of adjacent application instance(s).
description:The GET method is to retrieve the information of adjacent application instances. Upon success, the response contains entity body with the list of available application instance information.
description:The GET method is to retrieve the information of adjacent application instances. Upon success, the response message content contains the list of available application instance information.
description:Complex attributes to be excluded from the response. See clause 6.18 in ETSI GS MEC 009 [4] for details. The API producer should support this parameter.