Smart Data Models’ Candidates repository now includes a new candidate standard from the telecom world: camara-apis, with 7 candidate models translated from the CAMARA network APIs: quality on demand, device location and geofencing, crowd data and device reachability. The CAMARA specifications are published under Apache-2.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.
About CAMARA
CAMARA is the open-source project of the Linux Foundation, run with the GSMA Open Gateway initiative, that defines network APIs exposed in the same way by mobile operators around the world. Each API is an OpenAPI specification in its own GitHub repository, released in coordinated meta-releases. This candidate uses the latest public release of each API on 13 November 2026: the Fall25 releases of QualityOnDemand, DeviceLocation, RegionDeviceCount and DeviceReachabilityStatus, and the Sync26 release (1.0.0) of PopulationDensityData.
The models
| Model | CAMARA API | What it describes | Attributes |
|---|---|---|---|
QosProfile |
qos-profiles 1.1.0 | A network quality profile: target and maximum rates, latency, jitter, loss, priority | 24 |
SessionInfo |
quality-on-demand 1.1.0 | A quality-on-demand session between a device and an application server | 18 |
DeviceLocation |
location-retrieval 0.5.0 | The network-based location area of a device | 10 |
GeofencingSubscription |
geofencing-subscriptions 0.5.0 | A subscription to area-entered / area-left events for a device | 15 |
CellPopulationDensityData |
population-density-data 1.0.0 | Estimated number of people in a geohash cell for an hourly slot | 14 |
RegionDeviceCount |
region-device-count 0.2.0 | Number of devices in an area and time window, with filters | 13 |
DeviceReachabilityStatus |
device-reachability-status 1.1.0 | Whether a device is reachable, for data and/or SMS | 10 |
One consistent example scenario
CAMARA has no open data (operators expose the APIs only to registered consumers), so the examples are synthetic, and say so. They follow an evening event at Puerta del Sol in Madrid: a QoD session with a QOS_L profile carries a live-video uplink, a field team’s device is located, watched by a geofence and checked for reachability, and the crowd is described by the population density of geohash cell ezjmgtw and a device count for the square. No real phone numbers are used: device identifiers are CAMARA’s own example number +123456789 and documentation IP addresses.
Translation notes
- CAMARA names, verbatim. Every field keeps its CAMARA name. Entities are named after the CAMARA component, or after the API when the component is generic or a response wrapper (
DeviceLocation,GeofencingSubscription,RegionDeviceCount,DeviceReachabilityStatus). Each@contextmaps terms to their place in the released OpenAPI file. - Linked. A QoD session points to its
QosProfileas an NGSI-LD Relationship. - Ready for geo-queries. Location, geofence, region and geohash cell entities get an NGSI-LD
locationbuilt from CAMARA’s own areas. It is the only addition to the CAMARA content. - No secrets. Delivery credentials (access tokens) of sessions are left out. Device identifiers are personal data, so deployments should use pseudonymous ids where possible.
Try it, and tell us what’s missing
These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open questions are overlap with CrowdFlowObserved (Transportation), Device and NetworkConnection. Natural next steps are the Connected Network Type and Device Roaming Status APIs, QoS provisioning, Edge Cloud and Network Slice Booking.
Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/camara-apis

