Merge branch 'STF625' into 'master'

| yes | `/mts_sessions/{sessionId}` | |

------

## MEC015 v2.2.1 (Not published yet)

## MEC015 v2.2.1

References:

* https://www.etsi.org/deliver/etsi_gs/MEC/001_099/015/02.02.01_60/gs_mec015v020201p.pdf

* https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/tree/v2.2.1

* https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/v2.2.1/BwManagementApi.yaml

* https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/v2.2.1/TrafficSteeringApi.yaml

* https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/stf644/BwManagementApi.yaml

* https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/stf644/TrafficSteeringApi.yaml

### Bandwidth Management API Endpoints

| Endpoint | Sandbox Usage |Notes |

| ---------- | --------------------- | -------------- |

| [/bw_allocations](https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/v2.2.1/BwManagementApi.yaml#/bwm)  | GET - Retrieve information about a list of bandwidthAllocation resources <br><br> Query input: <ul><li> app_instance_id:  Retrieve information about a list of bandwidthAllocation associated with appInsId <li> app_name: Retrieve information about a list of bandwidthAllocation associated with appName <li> session_id: Retrieve information about a list of bandwidthAllocation associated with allocationId <li> If no query parameter passed, it returns with the list of all the bandwidth allocation resources </ul> <br><br> POST -  Create a bandwidthAllocation resource <br><br>Returns a bandwidth allocation resource information along with unique allocationId.| As a MEC Sandbox user, I use this endpoint to list down all the bandwidth allocation resource allocation with/without using query parameters <br><br> As a MEC Sandbox user, I use this endpoint to create a bandwidth allocation resource allocation based on requestType (Application / Session Specific allocation), allocationDirection (uplink/downlink/symmetrical), sessionFilter, fixedAllocation values and allocate each resource with a unique allocationId | 

| [/bw_allocations/{allocationId}](https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/v2.2.1/BwManagementApi.yaml#/bwm)  |   GET -  Retrieve information about a specific bandwidthAllocation  <br><br> Returns specific bandwidth allocation resource information <br><br> PUT  -   Update the information about a specific bandwidthAllocation <br><br> PATCH - Modify the information about a specific existing bandwidthAllocation by sending updates on the data structure. <br><br> Returns an updated bandwidth allocation resource information for both PUT/PATCH method <br><br> DELETE - Remove a specific bandwidthAllocation      | <br><br> **As a MEC Sandbox user, I use this endpoint to update/retrieve/delete a specific bandwidth allocation resource** <br><br>  As a MEC Sandbox user, I use this endpoint to retrieve bandwidth allocation resource information of specific allocationId.  <br><br> As a MEC Sandbox user, I use this endpoint to update/replace a bandwidth resource allocation information for a specific allocationId with the requested changes of BwInfo type. <br><br> As a MEC Sandbox user, I use this endpoint to partially update a bandwidth resource allocation information for a specific allocationId with the requested changes in BwInfoDelta type, In which user is allowed to change some of the attributes.  <br><br>  As a MEC Sandbox user, I use this endpoint to delete bandwidth allocation resource information of specific allocationId.

| [/bw_allocations/{allocationId}](https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api/-/blob/v2.2.1/BwManagementApi.yaml#/bwm)  |   GET -  Retrieve information about a specific bandwidthAllocation  <br><br> Returns specific bandwidth allocation resource information <br><br> PUT  -   Update the information about a specific bandwidthAllocation <br><br> PATCH - Modify the information about a specific existing bandwidthAllocation by sending updates on the data structure. <br><br> Returns an updated bandwidth allocation resource information for both PUT/PATCH method <br><br> DELETE - Remove a specific bandwidthAllocation | <br><br> **As a MEC Sandbox user, I use this endpoint to retrieve/update/delete a specific bandwidth allocation resource** <br><br>  As a MEC Sandbox user, I use this endpoint to retrieve bandwidth allocation resource information of specific allocationId.  <br><br> As a MEC Sandbox user, I use this endpoint to update/replace a bandwidth resource allocation information for a specific allocationId with the requested changes of BwInfo type. <br><br> As a MEC Sandbox user, I use this endpoint to partially update a bandwidth resource allocation information for a specific allocationId with the requested changes in BwInfoDelta type, In which user is allowed to change some of the attributes.  <br><br>  As a MEC Sandbox user, I use this endpoint to delete bandwidth allocation resource information of specific allocationId.

### Traffic Steering API Endpoints

| Endpoint | Sandbox Usage |Notes |

### VIS API

| Supported | Endpoint |  Notes:   |

| --------- | -------- | --------- |

| No        | `/queries/uu_unicast_provisioning_info` | deferred for future consideration |

| Yes       | `/queries/uu_unicast_provisioning_info` |    |

| Yes       | `/provide_predicted_qos`                |    |

| Yes       | `/publish_v2x_message`                  |    |

| Yes       | `/subscriptions`                        |    |

| Yes       | `/subscriptions/{subscriptionId}`       |    |

| No        | `/queries/uu_mbms_provisioning_info`    | deferred for future consideration |

| No        | `/queries/pc5_provisioning_info`        | deferred for future consideration |

| Yes       | `/provide_predicted_qos`                |                                   |

| No        | `/publish_v2x_message`                  | deferred for future consideration |

| No        | `/subscriptions`                        | deferred for future consideration |

| No        | `/subscriptions/{subscriptionId}`       | deferred for future consideration |

## MEC 030 v2.2.1

### Query Endpoints

| **Endpoint**    | **Sandbox Usage**          | **Notes**          |

| ----------------|--------------------------- | ------------------ |

| [/provide_predicted_qos](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs030-vis-api/raw/v2.2.1/MEC030_V2XInformationService.yaml#/QoS/predicted_qosPOST) <br><br>This resource is queried to provide predicted QoS of a vehicular UE based on potential route information. Each UE may have different potential routes under consideration. Route information includes route origin and destination; intermediate waypoints may also be provided. Estimated journey start time and arrival time at each location may also be provided. | Input is a set of potential routes that a vehicle may consider for a journey. <br><br> Note: potential routes having the same origin and destination, journey start time and differing intermediate waypoints may be considered as alternatives of a specific journey. <br><br> Output is the predicted QoS, in the form of Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ), as defined in ETSI TS 136 214.  The network emulation algorithms used to calculate RSRP and RSRQ for MEC 012 RNIS are used to caluclate perdicted QoS for MEC 030. | As a Sandbox user, I can use this call to receive predictions of the radio signal conditions expected to be experienced during journey time for different potential routes I may consider (for the same trip or for different planned trips). <br><br> The Sandbox has an internal Prediction Function (PF) which receives route information (route locations, optionally with visiting time information) as input and provides predicted RSRP and RSRQ values for each location of the communicated potential route as output.  <br><br>  The Prediction Function considers diurnal traffic patterns for each zone based on estimated user activity in those areas throughout the day and the predicted QoS values are adjusted accordingly if the visiting time information is also provided in the request depending on the congestion status in those areas around the requested time. |

| [/queries/uu_unicast_provisioning_info](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs030-vis-api/raw/v2.2.1/MEC030_V2XInformationService.yaml#/queries/prov_info_uu_unicastGET) | GET - Retrieve provisioning information for V2X communication over Uu unicast.| As a MEC Sandbox user, I use this endpoint to  retrieve provisioning information required for V2X communication over Uu unicast based on the _location_info_.

| [/provide_predicted_qos](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs030-vis-api/raw/v2.2.1/MEC030_V2XInformationService.yaml#/QoS/predicted_qosPOST) <br><br>This resource is queried to provide predicted QoS of a vehicular UE based on potential route information. Each UE may have different potential routes under consideration. Route information includes route origin and destination; intermediate waypoints may also be provided. Estimated journey start time and arrival time at each location may also be provided. | Input is a set of potential routes that a vehicle may consider for a journey. <br><br> Note: potential routes having the same origin and destination, journey start time and differing intermediate waypoints may be considered as alternatives of a specific journey. <br><br> Output is the predicted QoS, in the form of Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ), as defined in ETSI TS 136 214.  The network emulation algorithms used to calculate RSRP and RSRQ for MEC 012 RNIS are used to caluclate perdicted QoS for MEC 030. | As a Sandbox user, I can use this call to receive predictions of the radio signal conditions expected to be experienced during journey time for different potential routes I may consider (for the same trip or for different planned trips). <br><br> The Sandbox has an internal Prediction Function (PF) which receives route information (route locations, optionally with visiting time information) as input and provides predicted RSRP and RSRQ values for each location of the communicated potential route as output.  <br><br>  The Prediction Function considers diurnal traffic patterns for each zone based on estimated user activity in those areas throughout the day and the predicted QoS values are adjusted accordingly if the visiting time information is also provided in the request depending on the congestion status in those areas around the requested time.

| [/publish_v2x_message](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs030-vis-api/raw/v2.2.1/MEC030_V2XInformationService.yaml#/V2X_msg/v2x_messagePOST) | POST - Used to publish a V2X message by a service consumer (e.g. a MEC application or a MEC platform) to VIS to notify the subscribed service consumers. | As a MEC Sandbox user, I use this endpoint to publish a V2X message to VIS who will then notify the subscribed service consumers.

| [/subscriptions](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs030-vis-api/raw/v2.2.1/MEC030_V2XInformationService.yaml#/subscription) | GET - Retrieve information about a list of subscriptions. <br><br> Query input: <ul><li> subscription_type:  Query parameter to filter on a specific subscription type (supported values are prov_chg_uu_uni and v2x_msg). <li> If query parameter is not passed, it returns with the list of all the subscriptions. </ul> <br> POST - Create a specific subscription type (supported subscription types are ProvChgUuUniSubscription, and V2xMsgSubscription). <br><br> Returns subscriptions along with _href_ which identifies each subscription uniquely. | As a MEC Sandbox user, I use this endpoint to list down all the subscriotions with/without using query parameters. <br><br> As a MEC Sandbox user, I use this endpoint to create a subscription based on subscription type (supported values are ProvChgUuUniSubscription, and V2xMsgSubscription), callbackReference, and filterCriteria. |

| [/subscriptions/{subscriptionId}](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs030-vis-api/raw/v2.2.1/MEC030_V2XInformationService.yaml#/subscription) | GET -  Retrieve information about a specific subscription.  <br><br> Returns specific subscription resource. <br><br> PUT - Update the information about a specific subscription. <br><br> Returns an updated subscription resource. <br><br> DELETE - Remove a specific subscription | <br><br> **As a MEC Sandbox user, I use this endpoint to retrieve/update/delete a specific subscription resource** <br><br>  As a MEC Sandbox user, I use this endpoint to retrieve subscription resource by providing a specific subscriptionId.  <br><br> As a MEC Sandbox user, I use this endpoint to update/replace a subscription by providing a specific subscriptionId with the requested changes of supported subscription type. <br><br>  As a MEC Sandbox user, I use this endpoint to delete subscription resource of specific subscriptionId.

 No newline at end of file

    * MEC011 - Application Enablement Service

    * MEC012 - Radio Network Information Service

    * MEC013 - Location Service

    * MEC015 - Traffic Management APIs

    * MEC016 - Device application interface (DAI)

    * MEC021 - Application Mobility Service

    * MEC028 - WLAN Access Network Information Service

|MEC011 | [Edge Platform Application Enablement](MEC011.md)

|MEC012 | [Radio Network Information Service](MEC012.md)

|MEC013 | [Location Service](MEC013.md)

|MEC015 | [Traffic Management APIs](MEC015.md)

|MEC016 | [Device application interface](MEC016.md)

|MEC021 | [Application Mobility Service](MEC021.md)

|MEC028 | [WLAN Access Network Information Service](MEC028.md)