Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Location subscription API #272

Open
JoachimDahlgren opened this issue Nov 4, 2024 · 1 comment
Open

Location subscription API #272

JoachimDahlgren opened this issue Nov 4, 2024 · 1 comment
Labels
backlog enhancement New feature or request

Comments

@JoachimDahlgren
Copy link
Collaborator

JoachimDahlgren commented Nov 4, 2024

Summary

Introduce a new location-subscription API to make it possible for an application to receive device location information events.

Background

In the early days of Device Location is was discussed if it should be possible not only to retrieve location information but also to subscribe to location information. At that time, such API was considered to sensitive to provide. Since then, CAMARA has made great progress in the Identity and Consent working group and there are today guidelines on how to handle API access and consent management in a consistent way https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md

Use case

While the geofencing-subscription API allow consumers to create subscriptions for their devices to receive notifications when a device enters or exits a specified area, a location-subscription API allows the API consumers to continuously monitor the location of a device. This is useful for tracking devices and valuable goods.

A subscription based API will be more convenient than continuously calling the location-retrieval API.

Implementation

It should be noted that subscribing to location information is supported by the most common location related APIs such as 3GPP SCEF/NEF T8 monitoring events , 3GPP GMLC Nglmc and OMA Mobile Location Protocol.

@JoachimDahlgren JoachimDahlgren added the enhancement New feature or request label Nov 4, 2024
@jlurien
Copy link
Collaborator

jlurien commented Nov 14, 2024

Hi @JoachimDahlgren,

I think that proposals for new APIs have now to be submitted first to the API Backlog WG. Eventually, if API is accepted, it would fit within the scope of DeviceLocation WG, but it would be good to know if some operator is interested in implementing this potential new API, or is it something worthy of being considered for sandbox incubation.

As part of the proposal, another aspect to consider is when the events would be triggered. Periodically (time-based) even if the device has not moved, when the difference between the current and the past notified location reaches certain distance, or a mix or both.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants