2024-04-09 Device Location - Meeting Minutes

Date

09 Apr 2024

Attendees & Representation

Type @ and your name to indicate your attendance

Community: Jose Luis Urien Ludovic Robert Fernando Prado Cabrillo Rafal Artych Ákos Hunyadi Cetin Alpaycetin, Joachim Dahlgren, Chintan Lodariya (Infosys) , Javier Carro, Ming Hui Foo

Agenda

• Open issues and PRs
• Any other business

Minutes

New

• Issue: Mandate '+' in all phoneNumber formats
  
  • PR: Make '+' mandatory for phoneNumber - Location Retrieval / Location Verification
    • Merged
  • PR for Geofencing: Make '+' mandatory for phoneNumber
    • Approved
      • Merged during the meeting.

• Ongoing issue: Remove API from info.title

  • New PR: Remove API from title and align use of Device as prefix
    • Approved
      • Merged during the meeting.

• PR: Geofencing feature file
  
  • Template not filled
  • Discuss licensing header
    • To be aligned in Commonalities as not sure we have ruling for this.
    • Akos will check internally
  • Discuss alignment to guidelines

• Issue: Cyclic reference in location-verification
  • Commented. It should not be a problem the current specification.
    • We keep it open for now

• Issue: Semantics of the absence of 'maxAge'
  • Discuss in meeting
    • Not sure why this 60 seconds limit.
    • Apply for Retrieval & Verification
    • We can change: 
      • Alternative (1) will be to change this limit value from 60 to x
        • if x=0: We have to specify that 0 means 'very recent' location (expectation from request is get the device location right now). If not able 'unknown' should be sent.
        • if x=5 (or other >0): We keep semantic of maxAge unchanged
      • Alternative (2) will to state that if maxAge not value it means real time location is requested.
      • Alternative (3) is to add additional parameter to explicitly ask for current location.
    • Preference from the team to alternative (1) but we keep the discussion open.
    • if maxAge is not valued then we expect to retrieve the latest location (that could be 2 hours ago).
    • Javier also opened the discussion about improving the accuracy limit (2000 meters as of now).

Ongoing

• Implement use of linting rule set for Device Location API

  • New PRs: Introducing corrections for yamllint and Adding configuration for Github Actions with linting ruleset
  • PR#166 Rafal will regenerate the linter & once done the PR will be merge → Done and approved
    • Merged during the meeting
  • PR#167: to be merged after #166 → Approved
    • #167 merged mysteriously during the meeting  
      • Rafal will double check
  • Double-check and merge

• Add Test Definition for location Retrieval #119

  • 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 → Working internally on details
    • Toyeeb to check with GSMA conformance → Update?
    • Orange is working on the testing too and will provide feedback soon. → Update? 

Waiting for Commonalities outcome, still open there

• Add x-correlator as specified in the guideline

  • Following PR Created:
    • Geofencing #174
      • Discussion about x-correlator open in commonalities
        • camaraproject/Commonalities#164
        • Suggestion to keep this PR open till commonalities outcome
      • Already merged

• Are we happy with security scope for geofencing
  • Scope name should reflect the date provided by the notification (not geofencing:subscriptions:write but more precise like geofencing:subscriptions:read-location )
  • Discussion on this topic in progress in Commonalities (camaraproject/Commonalities#163)

• Geofencing - Adding a value in Termination Reason value enum

  • Discussion in progress in Commnonalities: camaraproject/Commonalities#153
  • Related issues in DeviceStatus and QoD

• Subscription related issues → Proposal in TSC to setup a dedicated workshop

  • Geofencing API - Add Subscription type 'area-left-or-entered' to subscribe to both event in one time

    • Issue in Commonalities Subscription-Issue2: Allow event consumers to subscribe to more than one event types with a single subscription
  • Geofencing API - Defining a standard behavior for first event
    • Issue in Commonalities Issue 140

• Geofencing API - Add "format: uri" to notificationUrl

  • Issue in commonalities

Long term discussions

Administrative Code Area

• New Issue #83, with formal requirements from GSMA Product track
  • Document uploaded by TEF with a proposal.
  • Review priority and next steps → Clarify this:
    • More generally probably we need to have feedback loop with GSMA team about API work (and review the priority as focus could change)
      • Done during last TSC - see here: https://wiki.camaraproject.org/display/CAM/2024-03-21+TSC+Minutes

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.

  
  

• Issue #85
  • As requested by Joachim, issue 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

Action items