Newer
Older
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
content:
application/json:
schema:
type: array
minItems: 0
items:
$ref: '#/components/schemas/TransportInfo'
links:
getTransportInfo:
$ref: '#/components/links/GetTransportInfo'
Error.400:
description: >-
Bad Request.
It is used to indicate that incorrect parameters were passed to the request.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
text/plain:
schema:
$ref: '#/components/schemas/Empty'
Error.401:
description: >-
Unauthorized.
It is used when the client did not submit the appropriate credentials.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
text/plain:
schema:
$ref: '#/components/schemas/Empty'
Error.403:
description: >-
Forbidden.
The operation is not allowed given the current status of the resource.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
Error.404:
description: >-
Not Found.
It is used when a client provided a URI that cannot be mapped
to a valid resource URI.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
text/plain:
schema:
$ref: '#/components/schemas/Empty'
Error.409:
description: >-
Conflict.
The operation cannot be executed currently, due to a conflict with
the state of the resource. Typically, this is because the application
instance resource is in NOT_INSTANTIATED state.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
text/plain:
schema:
$ref: '#/components/schemas/Empty'
Error.412:
description: >-
Precondition Failed.
It is used when a condition has failed during conditional requests,
e.g. when using ETags to avoid write conflicts.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
text/plain:
schema:
$ref: '#/components/schemas/Empty'
Error.429:
description: >-
Too Many Requests.
It is used when a rate limiter has triggered.
content:
application/problem+json:
schema:
$ref: '#/components/schemas/ProblemDetails'
text/plain:
schema:
$ref: '#/components/schemas/Empty'
requestBodies:
ApplicationsSubscriptions:
content:
application/json:
schema:
$ref: '#/components/schemas/SerAvailabilityNotificationSubscription'
description: >-
Entity body in the request contains a subscription to the MEC
application termination notifications that is to be created.
required: true
Services:
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceInfo'
description: >-
New ServiceInfo with updated "state" is included as entity body of the
request
required: true
Services.Post:
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceInfo.Post'
description: >-
New ServiceInfo with updated "state" is included as entity body of the
request
required: true
ServicesServiceId:
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceInfo'
description: >-
New ServiceInfo with updated "state" is included as entity body of the
request
required: true
ServiceAvailabilityNotification:
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceAvailabilityNotification'
required: true
callbacks:
ServiceAvailabilityNotification:
'{$request.body#/callbackReference}':
post:
description: >-
'Represents the service availability information that
is used in the following cases
- when the MEC platform announces the newly available
services to the authorized relevant MEC applications (e.g.
the applications that indicate the services as "optional"
or "required") that are subscribed to the corresponding
service availability notifications
- when the MEC platform notifies the authorized relevant
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
applications that are subscribed to the corresponding
service availability notifications about the service availability changes.'
operationId: ServiceAvailabilityNotification_POST
tags:
- callbacks
requestBody:
$ref: '#/components/requestBodies/ServiceAvailabilityNotification'
responses:
'200':
description: Expected responses from callback consumer, if it accepts the callback
links:
GetIndividualmecService:
operationId: ServicesServiceId_GET
description: The `serviceId` value returned in the response can be used as the `serviceId` parameter in `GET /services/{serviceId}`
parameters:
serviceId: '$response.body#/serviceId'
PutIndividualmecService:
operationId: ServicesServiceId_PUT
description: The `serviceId` value returned in the response can be used as the `serviceId` parameter in `PUT /services/{serviceId}`
parameters:
serviceId: '$response.body#/serviceId'
GetTransportInfo:
operationId: AppServices_POST
description: The `id` value returned in the response can be used as the `transportId` parameter in `POST /applications/{appInstanceId}/services`. The first transport is provided as the link as wildcards are not supported
parameters:
transportId: '$response.body#/0/id'
GetIndividualmecSerMgmtApiSubscription:
operationId: ApplicationsSubscription_GET
description: The `subscriptionId` value returned in the response can be used as the `subscriptionId` parameter in `GET /applications/{appInstanceId}/subscriptions/{subscriptionId}`
parameters:
description: regex = \/mec_service_mgmt\/v1\/applications\/.*\/subscriptions\/.*\/(.*);subscriptionId = href.match(regex)[1];// where "href" is an attribute within the subscription attribute within the _links attribute
subscriptionId: 'TBC'
DelIndividualmecSerMgmtApiSubscription:
operationId: ApplicationsSubscription_DELETE
description: The `subscriptionId` value returned in the response can be used as the `subscriptionId` parameter in `DELETE /applications/{appInstanceId}/subscriptions/{subscriptionId}`
parameters:
description: regex = \/mec_service_mgmt\/v1\/applications\/.*\/subscriptions\/(.*);subscriptionId = href.match(regex)[1];// where "href" is an attribute within the subscription attribute within the _links attribute
subscriptionId: 'TBC'
GetIndividualmecSerMgmtApiSubscriptionLinkList:
operationId: ApplicationsSubscription_GET
description: The `subscriptionId` value returned in the response can be used as the `subscriptionId` parameter in `GET /applications/{appInstanceId}/subscriptions/{subscriptionId}`
parameters:
description: regex = \/mec_service_mgmt\/v1\/applications\/.*\/subscriptions\/(.*);subscriptionId = href.match(regex)[1];// where "href" is an attribute within the subscription attribute within the _links attribute
subscriptionId: 'TBC'
DelIndividualmecSerMgmtApiSubscriptionLinkList:
operationId: ApplicationsSubscription_DELETE
description: The `subscriptionId` value returned in the response can be used as the `subscriptionId` parameter in `DELETE /applications/{appInstanceId}/subscriptions/{subscriptionId}`
parameters:
description: regex = \/mec_service_mgmt\/v1\/applications\/.*\/subscriptions\/(.*);subscriptionId = href.match(regex)[1];// where "href" is an attribute within the subscription attribute within the _links attribute
subscriptionId: 'TBC'
examples:
ServiceInfo:
value:
serInstanceId: 'ServiceInstance123'
serName: 'ExampleService'
serCategory:
href: 'catItem1'
id: 'id12345'
name: 'RNI'
version: 'version1'
version: 'ServiceVersion1'
state: 'ACTIVE'
transportInfo:
id: 'TransId12345'
name: 'REST'
description: 'REST API'
type: 'REST_HTTP'
protocol: 'HTTP'
version: '2.0'
endpoint:
uris:
- '/mecSerMgmtApi/service/EntryPoint'
security:
oAuth2Info:
grantTypes:
- 'OAUTH2_CLIENT_CREDENTIALS'
tokenEndpoint: '/mecSerMgmtApi/security/TokenEndPoint'
serializer: 'JSON'
ServiceInfoList:
value:
- serInstanceId: 'ServiceInstance123'
serName: 'ExampleService'
serCategory:
href: 'catItem1'
id: 'id12345'
name: 'RNI'
version: 'version1'
version: 'ServiceVersion1'
state: 'ACTIVE'
transportInfo:
id: 'TransId12345'
name: 'REST'
description: 'REST API'
type: 'REST_HTTP'
protocol: 'HTTP'
version: '2.0'
endpoint:
addresses:
- host: '192.0.2.0'
port: 8080
security:
oAuth2Info:
grantTypes:
- 'OAUTH2_CLIENT_CREDENTIALS'
tokenEndpoint: '/mecSerMgmtApi/security/TokenEndPoint'
serializer: 'JSON'