From efc6b7cf7b18b937862462cb47aba1c42a6f03d8 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 2 Oct 2026 07:50:13 +0100 Subject: [PATCH 1/3] Align-CommR4.4-qos-booking-and-assignment.yaml --- .../qos-booking-and-assignment.yaml | 21 ++----------------- 1 file changed, 2 insertions(+), 19 deletions(-) diff --git a/code/API_definitions/qos-booking-and-assignment.yaml b/code/API_definitions/qos-booking-and-assignment.yaml index 415f033..716fb51 100644 --- a/code/API_definitions/qos-booking-and-assignment.yaml +++ b/code/API_definitions/qos-booking-and-assignment.yaml @@ -68,11 +68,12 @@ info: - Check with the SIM provider whether a unique "secondary" phone number is already associated with each device, and use the secondary phone number to identify the intended device if available + # Additional CAMARA error responses The list of error codes in this API specification is not exhaustive. Therefore the API specification MAY not document some non-mandatory error statuses as indicated in `CAMARA API Design Guide`. - Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable Commonalities Release can be identified in the `API Readiness Checklist` document associated to this API version. + Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable Commonalities Release can be identified from the `x-camara-commonalities` field, the changelog and the metadata of the released API version. As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API. @@ -1232,24 +1233,6 @@ components: status: "SUCCESSFUL" statusInfo: "BOOKING_ACCEPTED" - BOOKING_FAILURE: - summary: Booking Failed - description: QoS Booking failed, `statusInfo` has additional info. No `bookingId` will be returned. - value: - totalDevices: 5 - remainingDevices: 5 - qosProfile: "QOS_MEDIA_BROADCAST" - startTime: "2025-10-27T15:00:00.000Z" - duration: 3600 - serviceArea: - areaType: "CIRCLE" - center: - latitude: 37.735851 - longitude: -127.10066 - radius: 100 - status: "FAILURE" - statusInfo: "SERVICE_NOT_AVAILABLE" - BOOKING_PENDING: summary: Booking Pending description: QoS Booking request is pending, `statusInfo` has additional info. No `bookingId` will be returned. From 0963098c12fe74ba0d5d1097dd67e0e4b9eebb65 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 2 Oct 2026 07:52:00 +0100 Subject: [PATCH 2/3] Align-CommR4.4-qos-booking.yaml --- code/API_definitions/qos-booking.yaml | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/code/API_definitions/qos-booking.yaml b/code/API_definitions/qos-booking.yaml index 77ca3b7..8d9edd5 100644 --- a/code/API_definitions/qos-booking.yaml +++ b/code/API_definitions/qos-booking.yaml @@ -55,11 +55,12 @@ info: - If the requested `qosProfile` exists but is currently not available for creating a booking, then the server will return an error with the `422 QOS_BOOKING.QOS_PROFILE_NOT_APPLICABLE` error code. + # Additional CAMARA error responses The list of error codes in this API specification is not exhaustive. Therefore the API specification MAY not document some non-mandatory error statuses as indicated in `CAMARA API Design Guide`. - Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable Commonalities Release can be identified in the `API Readiness Checklist` document associated to this API version. + Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable Commonalities Release can be identified from the `x-camara-commonalities` field, the changelog and the metadata of the released API version. As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API. @@ -692,12 +693,6 @@ components: Point: $ref: '../common/CAMARA_common.yaml#/components/schemas/Point' - Latitude: - $ref: '../common/CAMARA_common.yaml#/components/schemas/Latitude' - - Longitude: - $ref: '../common/CAMARA_common.yaml#/components/schemas/Longitude' - Device: $ref: '../common/CAMARA_common.yaml#/components/schemas/Device' From 36f0972248ff313a63834a40e547bf6b1f234002 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Fri, 2 Oct 2026 15:19:37 +0100 Subject: [PATCH 3/3] Correction --- code/API_definitions/qos-booking-and-assignment.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/qos-booking-and-assignment.yaml b/code/API_definitions/qos-booking-and-assignment.yaml index a950534..adc9bca 100644 --- a/code/API_definitions/qos-booking-and-assignment.yaml +++ b/code/API_definitions/qos-booking-and-assignment.yaml @@ -1727,4 +1727,4 @@ components: RETRIEVE_BOOKINGS_NO_ITEMS: summary: No bookings found for the device description: No bookings are found for the device, value contains only empty array - value: [] \ No newline at end of file + value: []