Description
This proposal has been reframed following the API Backlog discussion. It is now a scope enhancement of Predictive Connectivity Data (PCD) rather than a new V2X API family, and supersedes the earlier V2X Exposure API framing.
Route QoS Prediction adds trajectory-aware, per-segment QoS forecasting: an application submits a planned route (a list of waypoints) and receives a forecast of network conditions (latency, throughput, reliability) with a confidence value for each segment, before a device travels the route.
PCD already forecasts connectivity for an area or volume over time. This builds on that model and adds the route dimension. The specific delta is:
- route/corridor input instead of a polygon or geohash area;
- per-segment output in travel order instead of grid cells;
- numeric latency and throughput plus a confidence dimension, alongside PCD's categorical service levels;
- optional forecast-change subscriptions, in addition to PCD's one-shot asynchronous callback.
The API only produces the forecast. QoD invocation, route optimisation or selection, and application adaptation are outside the normative scope and are treated only as examples of API composition.
Use cases
- Emergency vehicle routing — forecast connectivity along an ambulance route to pre-configure a prioritised session on weak segments before arrival.
- Fleet / logistics route comparison — compare QoS forecasts across alternative routes and pick the best-connected corridor.
- Drone corridor validation — verify connectivity along a planned flight path before authorising it.
Related to
- Predictive Connectivity Data (proposed as a scope enhancement of this API)
- Connectivity Insights (subscriptions overlap to be discussed)
- TM Forum TMF759 / Private Optimized Connectivity (assessed as complementary, pending confirmation against the full TMF759 v5.0 specification)
Supporting material
- Scope enhancement:
documentation/API proposals/APIScopeEnhancement_Route_QoS_Prediction.md
- OpenAPI definition:
documentation/SupportingDocuments/route-qos-prediction.yaml (lint-clean against the CAMARA Commonalities ruleset)
- Presentation:
documentation/SupportingDocuments/Route QoS Prediction API.pptx
Description
This proposal has been reframed following the API Backlog discussion. It is now a scope enhancement of Predictive Connectivity Data (PCD) rather than a new V2X API family, and supersedes the earlier V2X Exposure API framing.
Route QoS Prediction adds trajectory-aware, per-segment QoS forecasting: an application submits a planned route (a list of waypoints) and receives a forecast of network conditions (latency, throughput, reliability) with a confidence value for each segment, before a device travels the route.
PCD already forecasts connectivity for an area or volume over time. This builds on that model and adds the route dimension. The specific delta is:
The API only produces the forecast. QoD invocation, route optimisation or selection, and application adaptation are outside the normative scope and are treated only as examples of API composition.
Use cases
Related to
Supporting material
documentation/API proposals/APIScopeEnhancement_Route_QoS_Prediction.mddocumentation/SupportingDocuments/route-qos-prediction.yaml(lint-clean against the CAMARA Commonalities ruleset)documentation/SupportingDocuments/Route QoS Prediction API.pptx