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

Subscription for Location Area #18

Closed
NoelWirzius opened this issue Jan 31, 2023 · 6 comments · Fixed by #98
Closed

Subscription for Location Area #18

NoelWirzius opened this issue Jan 31, 2023 · 6 comments · Fixed by #98

Comments

@NoelWirzius
Copy link

NoelWirzius commented Jan 31, 2023

Summary

Create a subscription mode for the DeviceLocation API. So that developers are informed if a device is leaving or entering the "radius". This is important for tracking devices for Presetting of Homesettings or for tracking of logistics and more.

Changes

For this there are several changes to be done

  • Adding new paths /subscriptions
    • Brining in new optional parameter
      • Based on /verify
      • EventType is an array which is giving the subscription mode
        • AREA_ENTERED = the device is leaving the defined radius
        • AREA_LEFT = the device is entering the defined radius
      • ExpireTime to set how long the subscription should be active
    • Activate Multiple Devices and Multiple Events
@NoelWirzius NoelWirzius changed the title Subscription for Device Subscription for Location Area Jan 31, 2023
@bigludo7
Copy link
Collaborator

Hello @NoelWirzius
I'm also interested to contribute.

For the area definition, do you think we can stick to the radius or do we have to extend with polygon (or multi polygon) definition ?

@RogerJL
Copy link

RogerJL commented Apr 25, 2023

How many devices should one be able to subscribe too?
Suppose all companies subscribes to all their registered users - ready to push ads when entering...

Note: I think the EventTypes are mixed up in the suggestion.

@akoshunyadi
Copy link
Contributor

As decided in #64 the endpoint should be implemented in a separate API
The name is to be discussed

@shilpa-padgaonkar
Copy link
Collaborator

please check this and provide feedback camaraproject/Commonalities#8 (comment)

@jgarciahospital
Copy link
Collaborator

Please considere this message as a formal inclusion of the GSMA OGW Product WS request to include Subscription/notification mechanism as part of OGW services.

camaraproject/Commonalities#8 (comment)

For the specific case of location verification, the request includes device location verification API to include such subscription/notification mechanism, which is usually called "geofencing" in certain fora. Examples of such funcionality in trems of input-outputs are also included, to be aligned with current subscription mechanism in this API.

Additional context
More details included in the formal request file, attached:

Camara Submission - Subscription_Notifications v2.docx

@ukkaps
Copy link
Contributor

ukkaps commented Sep 6, 2023

I guess areas should be pre-defined from network, hence developer should be able to retrieve the available areas defined in a CSP network to get subscribed to (i.e. a concert area/ Mall area). Developers won't be able to define new geofences or request for areas.

I stand to be corrected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants