How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ETSI MEC 021 Application Mobility Service API

The Application Mobility Service defined in ETSI GS MEC 021, which coordinates the relocation of a running application instance and its user context between MEC hosts as a device moves across the network.

ETSI MEC 021 Application Mobility Service API is one of 24 APIs that ETSI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Edge Computing, MEC, and Mobility. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 13 operations across 7 paths, organized into 4 resource areas, and defines 32 schemas. It is described by OpenAPI 3.1.0, at version 2.2.1.

Requests are made against a single base URL, https://localhost/amsi/v1.

13 operations 7 paths 32 schemas 2 DELETE5 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.2.1
Server
https://localhost/amsi/v1
Resource Areas
4

Paths & Operations 13

Across 7 paths, the API surfaces 13 operations — 2 DELETE, 5 GET, 4 POST, 2 PUT. They span 4 resource areas: app_mobility_services, subscriptions, adjacent_app_instances, notifications. Each is listed below with its method, path, parameters, and response codes.

app_mobility_services 6
GET
/app_mobility_services
Query multiple Application Mobility Service resources.
AppmobilityservicesGET 5 params → 200400401403404406429
POST
/app_mobility_services
Create an Application Mobility Service resource.
AppmobilityservicesPOST body → 201400401403404406429
GET
/app_mobility_services/{appMobilityServiceId}
Read an Application Mobility Service resource.
AppmobilityservicesGETAppmobilityserviceid 1 param → 200400401403404406429
PUT
/app_mobility_services/{appMobilityServiceId}
Update an individual Application Mobility Service resource.
AppmobilityservicesPUTAppmobilityserviceid 1 param body → 200400401403404406412422
DELETE
/app_mobility_services/{appMobilityServiceId}
Delete an individual Application Mobility Service resource.
AppmobilityservicesDELETEAppmobilityserviceid 1 param → 204401403404429
POST
/app_mobility_services/{appMobilityServiceId}/deregister_task
Timer based individual deregistration of an Application Mobility Service resource.
AppmobilityservicesDeregistertaskPOSTAppmobilityserviceid 1 param → 204401403404406429
subscriptions 5
GET
/subscriptions
Retrieve information of multiple subscriptions to notifications of Application Mobility Service event.
SubscriptionsGET 1 param → 200400401403404406429
POST
/subscriptions
Subscribe to notifications of Application Mobility Service event.
SubscriptionsPOST body → 201400401403404406415422
GET
/subscriptions/{subscriptionId}
Read information of subscription of Application Mobility Service.
SubscriptionsGETSubscriptionid 1 param → 200400401403404406429
PUT
/subscriptions/{subscriptionId}
Update an individual subscription to notification of Application Mobility Service event.
SubscriptionsPUTSubscriptionid 1 param body → 200400401403404406412422
DELETE
/subscriptions/{subscriptionId}
Terminate an individual subscription to notification of Application Mobility Service event.
SubscriptionsDELETESubscriptionid 1 param → 204401403404429
adjacent_app_instances 1
GET
/queries/adjacent_app_instances
Read information of adjacent application instance(s).
QueriesAdjacentappinstancesGET 5 params → 200400401403404406429
notifications 1
POST
/user_defined_notification
Delivers a notification from the application lifecycle management resource to the subscriber.
UserdefinednotificationPOST body → 204401403404429

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are AdjacentAppInfoSubscription (7 properties), MobilityProcedureSubscription (7 properties), MobilityProcedureNotification (6 properties), ProblemDetails (5 properties). Each schema is shown below with its type and property counts.

MobilityStatus1_
object
1 property 1 required
AssociateId
string
The data type of AssociateId is defined in ETSI GS MEC 012 [6].
AppMobilityServiceLevel1_
object
1 property 1 required
contextTransferState1_
string
If present, it represents the state of transferring the user context to another application instance.
subscriptionType1_
object
1 property 1 required
ProblemDetails
object
5 properties
RegistrationInfo
object
|- NOTE: The data type of AssociateId is defined in ETSI GS MEC 012 [6].
4 properties 1 required
AdjacentAppInstanceInfo
object
5 properties 3 required
MobilityProcedureSubscription
object
|- NOTE: At least one of callbackReference and websockNotifConfig shall be provided by the service consumer. If both are provided, it is up to AMS to choose an…
7 properties 2 required
AdjacentAppInfoSubscription
object
|- NOTE: At least one of callbackReference and websockNotifConfig shall be provided by the service consumer. If both are provided, it is up to AMS to choose an…
7 properties 2 required
SubscriptionLinkList
object
1 property 1 required
MobilityProcedureNotification
object
6 properties 4 required
ExpiryNotification
object
4 properties 3 required
AppMobilityServiceLevel
object
|- NOTE: APPMOBILITYNOTALLOWED: the current serving application instance continues to deliver the service to the device. The AMS will inform the MEP to perform…
1 property 1 required
TestNotification
object
2 properties 2 required
CommunicationInterface
object
1 property
TimeStamp
object
2 properties 2 required
LinkType
object
1 property 1 required
MECHostInformation
object
|- NOTE: This information can be structured to cater for host identification schemes that are more complex than a simple identifier, e.g. when referring to the…
2 properties 1 required
WebsockNotifConfig
object
2 properties
ServiceConsumerId
object
The identifier of service consumer requesting the Application Mobility Service, i.e. either the application instance ID or the MEC platform ID.
2 properties
DeviceInformation
object
If present, it specifies the device served by the application instance which is registering the Application Mobility Service.
3 properties 1 required
_links
object
Hyperlink related to the resource. This shall be only included in the HTTP responses and in HTTP PUT requests.
1 property 1 required
FilterCriteria
object
List of filtering criteria for the subscription. Any filtering criteria from below, which is included in the request, shall also be included in the response.
3 properties
FilterCriteria1
object
List of filtering criteria for the subscription. Any filtering criteria from below, which is included in the request, shall also be included in the response.
1 property
Subscription
object
The service consumer's subscriptions.
2 properties 2 required
_links1
object
Hyperlinks related to the resource.
2 properties 1 required
TargetAppInfo
object
Identifiers to associate the information of target application instance.
2 properties 1 required
_links2
object
Object containing hyperlinks related to the resource.
1 property 1 required
_links3
object
Object containing hyperlinks related to the resource.
1 property 1 required
_links4
object
Hyperlink related to the resource.
1 property 1 required
IpAddresses
object
Entry point information of the service as one or more pairs of IP address and port.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

MEC021_AppMobilityService.yaml Raw ↑

Other APIs ETSI publishes across the network.

ETSI MEC 011 Edge Platform Application Enablement API
ETSI MEC 012 Radio Network Information API
ETSI MEC 013 Location API
ETSI MEC 014 UE Identity API
ETSI MEC 015 Traffic Management APIs
ETSI MEC 016 UE Application Interface API
ETSI MEC 010-2 Application Package and Lifecycle Management APIs
ETSI MEC 028 WLAN Information API
ETSI MEC 029 Fixed Access Information API
ETSI MEC 030 V2X Information Services API
ETSI MEC 033 IoT API
ETSI MEC 040 MEC Federation Enablement API
Where this information came from

This is an independent, third-party profile of ETSI MEC 021 Application Mobility Service API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.