2024-05-07 Device Location - Meeting Minutes

Date

Attendees & Representation

Type @ and your name to indicate your attendance

Community: Ludovic Robert Jose Luis Urien Pinedo Cetin Alpaycetin Joachim Dahlgren Akos Hunyadi Fernando Prado Cabrillo Javier Carro 

Agenda

Minutes

Release Management

  • Meta-release Fall-24 - timeplan updated
    • https://lf-camaraproject.atlassian.net/wiki/display/CAM/Meta-release+Fall24
    • Expected Deliverables 
      • M0 - approved, but communication delayed (expected begin of next week)
      • M1 - 30/04
        • Scope of Commonalities finalised: 
        • Scope of ICM in work, focus on OIDC profile
        • The release process definition expects here already an alpha release of Comm & ICM, but they will come only later, at latest 2 weeks before the release candidates (for review by API Sub Projects)
      • M2 - 15/06
        • (Release candidate of Commonalities + ICM)
      • M3 - 15/06
        • First release candidate of DeviceLocation, starting of test implementations
      • M4 - 31/08
        • Last (stable) release candidate of target release from DeviceLocation
        • Release Criteria fulfilled (incl validation of the release candidate by two independent implementation of the API)
      • M5 - 15/09
        • public release done

Meeting discussion:

  • We will use QoD as example for release technical management.
  • This is the first iteration so we can expect slight change in future (we are learning by doing).
  • All projects part of this meta-release HAVE TO be aligned with Commonalities.
    • List of items are listed in Commonalities issue #175

New

Ongoing

  • PR: Geofencing feature file
    • Discuss licensing header
      • To be aligned in Commonalities as not sure we have ruling for this.
      • (Meeting Action) Akos will check internally → Feedback?
    • Some new comments
      • (Meeting Decision) Better to delay the discussion after Test definition definition OK.
    • Issue in Commonalities to discuss Enhancement of the Testing Guidelines by TEF
      • Jose from TEF will upload an example of Location Verification ATP once the commonalities guidelines are approved 
        • May be updated as discussions progress
      • Toyeeb to check with GSMA conformance → Update?
      • Orange is working on the testing too and will provide feedback soon. → Update? 
    • Dedicated workshop in Commonalities scheduled for May 16th

Waiting for Commonalities outcome, still open there

Review status of the following issues, agenda copied from last meeting minutes:

On hold discussions

Administrative Code Area

Implementation

Define guidelines for geofencing implementation

  • We need more comments from the team
  • Connected with Issue #85. A document with implementation guideline should cover this also.
    • As requested by Joachim, issue #85 will remain open until TEF uploads the document with more detail or the information is added to an API_documentation file to keep in the repo for future references.
      • Joachim: Should be also aligned/synchronized with Geofencing
  • On issue #133 we probably need to have a base agreement for Geofencing guidelines
    • 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.

AOB

Action items