2024-06-19 Population Density Data - Meeting Minutes

CAMARA Population Density Data API - Follow-up meeting #10 - 2024-06-19

June 19th, 2024

Attendees

Name

Company

Name

Company

Sachin Kumar

Vodafone

Gregory Lindner

Ericsson

Ludovic Robert 

 Orange

Rafal Artych

DT

Violeta Gonzalez Fernandez

Telefonica

Jorge Garcia

Telefonica

 

Population Density Data API minutes: https://lf-camaraproject.atlassian.net/wiki/display/CAM/Population+Density+Data+API+Minutes

Agenda

  • Approval of previous meeting minutes #9 and meeting agenda

  • Open issues and PRs

    • Issues: #12 #24

    • PR #25 #30 #32

  • Initial algorithm proposal review

  • Timeline and next steps

  • AoB

Open Issues & PRs

 

 

 

 

 

 

Issue#12

Telefonica

Discussion on API algorithm - Initial proposal

Issue#24

Telefonica

API access mechanism

PR#25

Telefonica

Documentation of API Algorithm

PR#30

Telefonica

RC2 version proposal

PR#32

Telefonica

RC2 additional merge

Approval of previous meeting minutes & documentation (1)

Meeting Minutes #9

 Approved

API proposal review (2)

Issue#24

Authentication/security discussion opened around the usage of 2-3 legged access tokens for this API(s).

  • API, as not including personal data (anonymized), is to be considered as a 2-legged access token.

  • To review if API specification needs to be modified accordingly @Ludovic Robert 

After offline and online discussion, decision is taken on:

  • Not modify security schema in the API code, as no different guidance in I&CM group is determined apart from OIDC

  • Include clarification text in API documentation, establishing that the usage of this API is determined by CAMARA rules, in this case 2-leggged as no personal data is treated.

Text to be included as RC2

Issue to be closed when PR30 merged

PR#30 & PR#32

RC2 proposal and additional commits.

→Closed, 0.1 version to be published and proposed to meta-release as "INITIAL" version

Initial algorithm proposal (3)

Issue#12

K-anonimization to be clarified (in which step it is implemented)

When and how the prediction of persons/users is done, based on the input (devices)

 

Continue offline review

AoB (4)

Next steps:

  • Adapt commonalities based on v0.4 (when ready)

  • Include additional documentation (e.g. user stories)

  • Include ATP

Discussion Summary

Issue/PR

Summary

Action/Decision

Issue/PR

Summary

Action/Decision

Issue#12

Discussion on API algorithm - Initial proposal

To continue

Issue#24

API access mechanism

Closed

PR#25

Documentation of API Algorithm

To continue discussion

PR#30

RC2 version proposal

Merged

PR#32

RC2 additional merge

Merged

AoB

 

 

Next steps

  1. Feedback on algorithm proposal→ Follow-up meeting #

  2. Close async mechanism #

  3. Parameter definitions #

  4. RC API spec agreement → Follow-up meeting #

  • Next call will be July 03rd, 2024