From af530ba9c3088e7f397b7e07d6ba33d3f61d347b Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Mon, 2 Feb 2026 11:26:00 +0100 Subject: [PATCH 1/2] Update User Storie for Predictive Connectivity Data --- .../Predictive-Connectivity-Data_User_Story.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md b/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md index 72bd5b2..aabd6bf 100644 --- a/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md +++ b/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md @@ -4,7 +4,7 @@ |---------|-------------| | **_Summary_** | The API provides the capability to get the estimation of connectivity delivered by 4G/5G networks along a volume/area for a future date, time and height. | | **_Actors and Scope_** | **Scope:**
- Retrieve predicted mobile connectivity (4G/5G) for a defined polygonal area, time interval, and height.
- Supports planning in aerial and terrestrial domains.

**Use Case 1 – Network Airspace Connectivity Information (forecast) for Flight Planning:**
- Delivers comprehensive analysis with data about mobile network coverage in specific geographic areas.
- Identifies “black volumes” to avoid drone disconnection risks.

**Use Case 2 – Autonomous Car:**
- Provides predicted mobile network coverage data along the vehicle route. | -| **_Pre-conditions_** | – The client must provide the following inputs:
1. **Requested Area:** polygonal area defined by coordinates (Required)
2. **Start Time** and **End Time:** future time window (Required)
3. **Service Level:** type of service needed (e.g., C2-Coms, Streaming) (Required)
4. **Technology:** 4G or 5G (Optional)
5. **Height** and **Precision** (as suggested in scope evolution discussions) | +| **_Pre-conditions_** | – The client must provide the following inputs:
1. **Requested Area:** polygonal area defined by coordinates forming a closed loop (Required)
2. **Start Time** future controlled time of departure (Required). **End Time:** ffuture controlled time of arrival (Required).
3. **Service Level:** type of service needed (e.g., C2, STREAM_4K) (Required)
4. **Technology:** 4G or 5G (Optional)
5. **Height** and **Precision** (as suggested in scope evolution discussions) | | **_Activities/Steps_** | - The client submits a request including the inputs listed above.
- The API responds with:
1. An array of cells (Geohash-encoded) with hourly connectivity predictions:
    - GC: Good Connectivity
    - MC: Marginal Connectivity
    - NC: No Connectivity
2. Layer thickness in meters (AGL)
– Output may optionally include **Signal Strength** instead of **Service Level**. | | **_Post-conditions_** | The requester obtains connectivity forecasts that support planning for flight or vehicle route safety based on mobile network availability. | | **_Exceptions_** | Several exceptions might occur during the PredictiveConnectivityData API operations:
- **Invalid input:** Required fields missing or incorrectly formatted (e.g., malformed polygon, missing Start/End Time or Service Level).
- **Unsupported values:** Inputs that exceed defined limits (e.g., time window too far in the future, unsupported technology type).
- **Unavailable data:** The requested area, time, or combination of parameters does not match any available prediction dataset. | From 3864da28b1e384efac8986df1843c5d223c1a447 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Tue, 10 Feb 2026 10:41:23 +0100 Subject: [PATCH 2/2] Apply suggestion from @eric-murray Co-authored-by: Eric Murray --- .../Predictive-Connectivity-Data_User_Story.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md b/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md index aabd6bf..fc37a06 100644 --- a/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md +++ b/documentation/API_documentation/Predictive-Connectivity-Data_User_Story.md @@ -4,7 +4,7 @@ |---------|-------------| | **_Summary_** | The API provides the capability to get the estimation of connectivity delivered by 4G/5G networks along a volume/area for a future date, time and height. | | **_Actors and Scope_** | **Scope:**
- Retrieve predicted mobile connectivity (4G/5G) for a defined polygonal area, time interval, and height.
- Supports planning in aerial and terrestrial domains.

**Use Case 1 – Network Airspace Connectivity Information (forecast) for Flight Planning:**
- Delivers comprehensive analysis with data about mobile network coverage in specific geographic areas.
- Identifies “black volumes” to avoid drone disconnection risks.

**Use Case 2 – Autonomous Car:**
- Provides predicted mobile network coverage data along the vehicle route. | -| **_Pre-conditions_** | – The client must provide the following inputs:
1. **Requested Area:** polygonal area defined by coordinates forming a closed loop (Required)
2. **Start Time** future controlled time of departure (Required). **End Time:** ffuture controlled time of arrival (Required).
3. **Service Level:** type of service needed (e.g., C2, STREAM_4K) (Required)
4. **Technology:** 4G or 5G (Optional)
5. **Height** and **Precision** (as suggested in scope evolution discussions) | +| **_Pre-conditions_** | – The client must provide the following inputs:
1. **Requested Area:** polygonal area defined by coordinates forming a closed loop (Required)
2. **Start Time** future controlled time of departure (Required). **End Time:** future controlled time of arrival (Required).
3. **Service Level:** type of service needed (e.g., C2, STREAM_4K) (Required)
4. **Technology:** 4G or 5G (Optional)
5. **Height** and **Precision** (as suggested in scope evolution discussions) | | **_Activities/Steps_** | - The client submits a request including the inputs listed above.
- The API responds with:
1. An array of cells (Geohash-encoded) with hourly connectivity predictions:
    - GC: Good Connectivity
    - MC: Marginal Connectivity
    - NC: No Connectivity
2. Layer thickness in meters (AGL)
– Output may optionally include **Signal Strength** instead of **Service Level**. | | **_Post-conditions_** | The requester obtains connectivity forecasts that support planning for flight or vehicle route safety based on mobile network availability. | | **_Exceptions_** | Several exceptions might occur during the PredictiveConnectivityData API operations:
- **Invalid input:** Required fields missing or incorrectly formatted (e.g., malformed polygon, missing Start/End Time or Service Level).
- **Unsupported values:** Inputs that exceed defined limits (e.g., time window too far in the future, unsupported technology type).
- **Unavailable data:** The requested area, time, or combination of parameters does not match any available prediction dataset. |