2024-06-18 Device Location - Meeting Minutes

DRAFT MINUTES

Date

Jun 18, 2024

Attendees & Representation

Type @ and your name to indicate your attendance

Community: ย @Ludovic Robert @Fernando Prado Cabrillo @Akos Hunyadi @Jose Luis Urien Pinedo @Surajj Jaggernath @Javier Carro @Joachim Dahlgren @Rafal Artychย 

Agenda

Minutes

New

  • Simplification of Device object - short term solution

    • Should device be made optional?

      • Team decision:ย  It's quite safe - OK for the team.

        • Akos raised the point aboutย requirement to enhance documentation in the API - should be global for all CAMARA API

        • Rafal indicated that it would be handled & finalized in Commonalities

    • Should networkAccessIdentifier be deprecated?

      • ย 

        • @Joachim Dahlgren asked to keep it.

        • For Telefonica & Orange it could be removed.

        • Rafal explained that in commonalities we propose to keep it but not use it

        • Team Decision: We keep it but not use it. We will add a test scenario for that.

    • Discussion during meeting

      • Discussion about the CIBA flow.

Ongoing

  • Issue:ย [Geofencing] Support for polygon area type

    • PR: Polygon area type added

    • Decision about adding support or not, making this support mandatory or not ?ย 

    • ย 

      • Does the following statement could be acceptable for first meta release: "We add the polygon. Circle management is mandatory while polygon is nice to have. " ?

        • We have still some time to discuss this.

    • How to managed not supported polygon:ย 

    • Team Decision: This one could be backlog-ed. Not for first meta release.

  • Issue: [Location-Retrieval]: addย POINTย as possible Location response

    • Some comments on the issue. Minimum right now is a CIRCLE with radius=1m, Is it not enough?

    • Discard point and rely on Circle?

      • Agreement (previous meeting) from @Jose Luis Urien Pinedo @Joachim Dahlgren and @Ludovic Robert to consider that 1m radius will be good enough (and no need for Point)

      • No further comments, can we close issue?

        • Action: Akos will check with Max if we can close it.

    • Related topic raised in last meeting, no new issue:

      • Should we lower minimum radius for location-verification?

        • @Javier Carro has still some discussion with legal team about privacy issue

      • Any update?

  • Define guidelines for geofencing implementationย 

    • No new comments

    • Last meeting:

      • Akos & Josรฉ proposed some suggestion - in particular to improve the subscription to allow consumer to indicate the 'reliability' expected.

      • Ludovic also raised the point above UC where we are not able to send any notification.... and we need to inform the consumer.

      • Discussion/Action: DT team can move forward with a PR with the proposal about adding triggerSensibility

    • New thoughts, can we create PR?

    • Not discussed with the team - Probably to be shift to the backlog.

Test plans

  • Commonalities guidelines approved and merged.

    • All test plans should be updated to follow them.

  • PR: Geofencing feature file

    • Discuss licensing header: (Meeting Action) Akos will check internally โ†’ย Feedback?

      • Check if Max is willing to do it.

ย 

AOB

Action items