THE LINUX FOUNDATION PROJECTS

Geofencing Subscriptions

API Description
Use Cases
  • Logistics and Fleet Operations: Logistics platforms can associate a connected tracking device with a shipment, vehicle or container and define geofences around relevant locations such as warehouses, distribution centres or delivery areas. When the device enters or leaves the subscribed area, the application can update the shipment status, confirm arrival or departure, trigger an operational workflow or alert the relevant team.
  • Industrial and smart-facility Monitoring: Industrial applications can subscribe to entry or exit events for connected equipment, vehicles or IoT devices operating within predefined zones. This can help detect unexpected movements, automate internal workflows or trigger additional checks when a device leaves an authorised operational area.
  • Safety-Zone Alerts for connected Devices: Applications can subscribe to geofence events for a connected device and trigger an alert when it enters a restricted or hazardous area, or when it leaves an expected zone. This can support safety workflows where the appropriate legal basis, user authorisation and local requirements are met.
  • Drone Fleet Coordination and first-response Operations: Applications can use geofence events as part of a broader operational solution for connected drones or other network-connected devices. Entering or leaving a predefined area can trigger workflow updates, coordination actions or safety checks.
  • Location-triggered Customer Experiences: Where permitted and appropriately authorised, retail, hospitality, mobility or event applications can react when a user device enters a predefined area. This can support contextual information, service activation or relevant offers without continuously polling for the device location.

See also at GSMA:

Benefits
  • Event-driven Automation: Enables applications to react when a device enters or leaves a predefined area without repeatedly requesting its location.
  • Reduced Polling and Integration Overhead: Allows developers to receive callback notifications only when the relevant geofence transition occurs.
  • Network-based Geofence Signal: Provides an independent network-derived event that can complement device-reported location information in location-dependent workflows.
  • Operational Efficiency: Helps automate shipment updates, safety checks, asset-related workflows and contextual service activation.
  • Flexible Subscription Controls: Allows API consumers to define subscription expiration, limit the maximum number of events and request an initial event when applicable.
  • Standardized Developer Integration: Provides a CAMARA interface that can be integrated consistently into logistics, industrial, IoT, safety and contextual-service applications.

API Portfolio: Location Services

Sub Project Wiki: Device Location
(incl. how to meet the team)

API Wiki: Device Location

API Repository: Device Location

API Repository Status: Incubating

API Status: Initial

API Version(s) and Release Date(s):

  • v0.1.0 (09.08.2024)
  • v0.3.0 (10.11.2024), Fall24 meta-release
  • v0.4.0 (10.03.2025), Spring25 meta-release
  • v0.5.0 (16.09.2025), Fall25 meta-release

API availability: Information which APIs are available in which country and network, and how to get access can be found on the GSMA public launch status page.

Be part of a collaborative community driving the future of global Telco APIs.

Join Today