MEC 016 Validation Issues during TTF043
This summary captures issues identified during the validation of ETSI MEC 016 API as part of TTF043 activities.
1. TC_MEC_MEC016_MEO_UEAPPCTX_001_BR
Description:
Check IUT response when a request with incorrect parameters is sent by a MEC Application.
Expected:
HTTP 400 Bad Request
Observed:
Server returns 500 Internal Server Error
2. TC_MEC_MEC016_MEO_UEAPPCTX_002_BR
Description:
Check IUT response when PUT is used with invalid input parameters.
Expected:
HTTP 400 Bad Request
Observed:
Server returns 500 Internal Server Error
3. TC_MEC_MEC016_MEO_UEAPPCTX_002_NF
Description:
Check IUT response when PUT is sent to a non-existent application context ID.
Expected:
HTTP 404 Not Found
Observed:
Server returns 204 No Content
4. TC_MEC_MEC016_MEO_UEAPPCTX_003_NF
Description:
Check IUT response when DELETE is sent to a non-existent application context ID.
Expected:
HTTP 404 Not Found
Observed:
Server returns 500 Internal Server Error
5. TC_MEC_MEC016_MEO_UEAPPLOC_001_BR
Description:
Check IUT response when a POST request is sent with invalid location availability parameters.
Expected:
HTTP 400 Bad Request
Observed:
Server returns 500 Internal Server Error – Not fixed
Recommendation
Update the MEC Sandbox implementation to ensure:
- Proper HTTP error codes (e.g., 404, 400) are returned as per ME API spec.
-
Locationheaders are included on successful POSTs. - Response payloads return complete and accurate field values.