Update MEC030.md

# MEC030 - V2X Information Service

# MEC030 - V2X Information Service

> _under development_

> _under development_input_for_STF625

This section describes how MEC030, V2X Information Service (VIS) operates within the MEC Sandbox.

The following tables list MEC Sandbox supported endpoints for each MEC030 API.

### VIS API

| Supported | Endpoint |  Notes:   |

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

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

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

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

| Yes | `/provide_predicted_qos` | to be implemented by STF625 |

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

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

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

_NOTE -- MEC 030 VIS API is planned to be delivered in STF625 Feature Set #1, April 2022._

_STF625 is scoped to include the /provide_predicted_qos endpoint.  All other endpoints are deferred for future consideration._

This section describes how MEC030, V2X Information Service operates within the MEC Sandbox.

## MEC 030 v2.1.1 (published, available on forge)

## MEC 030 v2.1.1 (published, available on forge)

### Query Endpoints

### Query Endpoints

| Endpoint     | Sandbox Usage             |Notes                |

| Endpoint     | Sandbox Usage             |Notes                |

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

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

| /queries/provide_predicted_qos <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. | 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 Link Performance Prediction (LPP) to be integrated as it plays the role of a 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> _LPP integration into the MEC Sandbox and the underlying AdvantEDGE open-source edge emulator is TBD._  |

| /queries/provide_predicted_qos <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 Link Performance Prediction (LPP) to be integrated as it plays the role of a 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> _LPP integration into the MEC Sandbox and the underlying AdvantEDGE open-source edge emulator is TBD._  |