Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

• Approval of previous meeting minutes and meeting agenda.

• Open issues and PRs

• Discussion Summary

  • Agenda 1: meta-release fall25 deliverables.

  • Agenda 2: YAML review of predictive-connectivity-data (https://github.com/camaraproject/PredictiveConnectivityData/pull/20 )

• AoB

Approval of previous meeting minutes

2025-05-27 PredictiveConnectivityData Minutes: [decision]

Open Issues & PRs

Discussion Summary

Agenda 1: meta-release fall25 deliverables:

• https://github.com/camaraproject/PredictiveConnectivityData/issues/9

  • API predictive-connectivity-data version 0.1.0 Release Tracker Management #14 - Done

  • API predictive-connectivity-data version 0.1.0 alignment with transversal #15

  • API predicitive-connectivity-data version 0.1.0 API Readiness Checklist #16 - Done

  • API predictive-connectivity-data version 0.1.0 functional enhancements #17

  • API predictive-connectivity-data version 0.1.0 testing enhancements #18

Agenda 2:

• The Airspace Connectivity Data API has been renamed to Predictive Connectivity Data (name of the working group in CAMARA).

• Asynchronous behavior has been added, similar to Population Density Data, via a callback mechanism. If the sink property is provided, the API will return a 202 and, once the response is ready, will send a POST request to the URL specified in the sink property of the request. To provide credentials for the callback, the sinkCredential property is also defined.

• The description has been improved. @Violeta González have added more details to the description provided, without changing your original text too much — mainly an explanation of the AGL term and a more detailed description of the asynchronous behavior and its associated errors.

• Status and statusInfo properties: Same logic as in Population Density Data, with 4 possible status values:

  • SUPPORTED_AREA: The whole request area is supported. Connectivity data for the entire requested area is returned.

  • PART_OF_AREA_NOT_SUPPORTED: Part of the requested area is outside the MNO’s coverage area. The cells outside the coverage area will have the layerConnectivities property with all items in the array set to ND.

  • AREA_NOT_SUPPORTED: The whole requested area is outside the MNO’s coverage area. No data will be returned.

  • OPERATION_NOT_COMPLETED: An error occurred during asynchronous processing of the request. This status will only be returned when the asynchronous API behavior is used.

• The 410 error code has been added.

• The only change that we did not include was adding the cellType to indicate "NO_DATA". For this API, considering that the connectivity value is an array and not a single value, it did not seem to fit well. In any case, this can be discussed further in the working group.

• The API has also been aligned with CAMARA commonalities in several areas.

AoB

• N/A

Action Points