Versions Compared

Old Version 1

changes.mady.by.user Ricardo Serrano Gutierrez

Saved on

compared with

New Version Current

changes.mady.by.user Jorge Garcia Hospital

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT MINUTES

Attendees


OrganizationName
OrangeLudovic Robert 
Charter CommunicationsChristopher Aubut Justin Pace 
CableLabsBen Hepworth 
TelefonicaVodafoneJorge Garcia Hospital 
Vodafone

Kevin Smith Eric Murray Kevin Smith 

EricssonThorsten Lohmar Jan Friman 
AT&TPierre Close 
T-Mobile US
KDDI
Slagen
Nokia
China Telecom
ZTE
KPN
GSMAReg Cox (Deactivated) Mark Cornall 
Centilion
Chunghwa Telecom
Deutsche Telekom

Noel Wirzius 


MTN

Krishna Venkatachalam Rachel



Agenda Proposal

  • Antitrust Policy
  • Approval of minutes of last conf. call
  • Recent Updates & Recap
  • Review of Action Points
  • Discussion

    • OGW Drop #4 APIs:  #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling), #63 (IMEI Fraud)

    • Other APIs:  #17 (Consent and Measurement),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info), 68 (Consent Resource URL), 70 (Quality by Design)

    • Governance: #4 (Structures and roles, RACI, Maintainers initiative)

  • Closing Clossing Issues

    • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #19 (Device Quality Indicator), #28 (Device Data Volume), #18 (Receive SMS), #28 (Device Data Volume)

  • AoB
  • Q&A

Antitrust Policy

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LinusFoundation.


 

New Procedures in API Backlog WG meetings

A number of improvements are under discussion with leadership team of OGW project (Henry), CAMARA Project (Markus), Product Definition WS (Helene) and TSC (Herbert). As of today, the WG adopted agreements are three:

  1. To close the agenda SEVEN DAYS BEFORE the conf. call.
    • In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.
    • Exceptional situations will be treated separately.
  2. New schedule of conf. calls **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)
    • 2nd Thursday of the month (10-11 CET)
    • 4th Thursday of the month (15-16 CET)
  3.  Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them. 

Meeting Minutes within Wiki instead of Github

...

Approval of minutes of last conf. call

  • Minutes of last API backlog WG call available here

    • DECISION: APPROVEDapproved

Recent Updates & Recap

TSC meeting 1st August:

...

 For clarity if any API is not a priority for OGW anymore at this point in time, we still expect they can progress independently in CAMARA.


Backlog table

Review of Action Points

17 CentillionNew Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement
The API template is available in PR#386.

Published new standards, Next meeting (this time) Nick will bring all the documentation and present everything putted together

The issue is not eligible to be closed yet.

MEETING UPDATE:

  • Not discussed
4

Governance

AP #

AP Owner

AP description

Related issue

Due date

Status

20240523-01API Backlog GovernanceRicardo to reach up TelecomXchange , Totogi and Netfocusin Technologies to see if the could connect next meetings23 18 2423/05/2024Open
2024052320240711-0701DT

Best interconnection: Review whether there is overlap with EdgeCloud subproject

Meeting Update:

  • No clear overlap with Edge Cloud
  • API anyway to be de-prioritised
  • Action closed
2023/05/2024Completed
20240627-01China Unicom, KDDI, Vodafone, DT

Check whether Tenure + Shutdown service + Number recycling fit in KYC (parts involved align internally)

Closed for Tenure and Number Recycling (accepted and repo created)

Shutdown Service pending to create repo. Codeowners to be required by email (China Unicom, China Telecom, Huawei) and reported to TSC.

Meeting Update:

  • Shutdown Service API also approved with new repository to be created
  • Codeowners /  Maintainers have been identified
  • Action closed
54 2 3428/06/2024

Completed

20240627-02API Backlog GovernanceNew use cases are usually proposed. Modify the Scope template to show this and approve5328/06/2024Completed
20240711-01Netfocusin TechnologiesSeek for support/commitment from the partners (technical implementation approach important)2411/07/2024Open
20240711-02TelefonicaProvide comments for dedicated network6011/07/2024Completed
20240711-03VodafoneCreate the template for network info6111/07/2024Completed
20240711-04MTN/Chenosis

IMEI Fraud: Check the material shared by Eric/GSMA regarding DeviceCheck, and validate the inclusion of the API in the Device Identifier group

Meeting Update:

  • IMEI Fraud will offer more information than GSMA Device Check service. MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense. Request for meeting already sent by GSMA.
  • Action to remain open until after meeting with GSMA is held

NOTE: Can be taken to TSC if agreement by end of Thursday

6311/07/2024Open
20240801-01Deutsche Telekom

Device Quality Indicator: To provide list of Maintainer/Codeowner

Meeting Update:

  • Information provided
  • Action closed
1916/08/2024Completed
20240801-02Deutsche Telekom

Device Data Volume: To provide list of Maintainer/Codeowner

Meeting Update:

  • Information provided
  • Action closed

28

16/08/2024Completed
20240801-03China Unicom

Shutdown ServiceStatus: To provide list of Maintainer/Codeowner

Meeting Update:

  • Information provided
  • Action closed

34

16/08/2024Completed
20240801-04Vodafone

Scope Enhancement for Network info:

To clarify if new API is proposed  in the Device Status Family or it's an enhancement over an existing API.

To clarify it's relationship with Open Gateway Telco Finder API.

Meeting Update:

  • Kevin opened PR #72 to complement Issue #66. Both still open.
  • Noel commented that this is likely to be accepted
  • New repository is likely to be required
  • Action to stay open until PR#72 is decided

NOTE: Can be taken to TSC if agreement by end of Thursday

6108/08/2024Open
20240801-05Cablelabs

Quality by Design: Clarification pending on the differences with current Mobile/Fixed QoD and Network info / Quality indicator APis / Connectivity Insights

Meeting Update:

  • Proposal is that QbD be a scope enhancement to Connectivity Insights
  • Will likely require new API, hence new repository required
  • QdD supporters will attend Connectivity Insights meeting next week to finalise proposal
  • Action to stay open until after next Connectivity Insights meeting

NOTE: Can be taken to TSC if agreement by end of Thursday

7008/08/2024Open

Discussion

Current Issues 

Netfocusin TechnologiesSeek for support/commitment from the partners (technical implementation approach important)2411/07/2024Open
20240711-04MTN/Chenosis

IMEI Fraud: Check the material shared by Eric/GSMA regarding DeviceCheck, and validate the inclusion of the API in the Device Identifier group

  • IMEI Fraud will offer more information than GSMA Device Check service. MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense. Request for meeting already sent by GSMA.
  • Action to remain open until after meeting with GSMA is held

Meeting Update:

6311/07/2024Open
20240801-04Vodafone

Scope Enhancement for Network info:

To clarify if new API is proposed  in the Device Status Family or it's an enhancement over an existing API.

To clarify it's relationship with Open Gateway Telco Finder API.

  • Kevin opened PR #72 to complement Issue #66. Both still open.
  • Noel commented that this is likely to be accepted
  • New repository is likely to be required
  • Action to stay open until PR#72 is decided

Meeting Update:

6108/08/2024Open
20240801-05Cablelabs

Quality by Design: Clarification pending on the differences with current Mobile/Fixed QoD and Network info / Quality indicator APis / Connectivity Insights

  • Proposal is that QbD be a scope enhancement to Connectivity Insights
  • Will likely require new API, hence new repository required
  • QdD supporters will attend Connectivity Insights meeting next week to finalise proposal
  • Action to stay open until after next Connectivity Insights meeting

Meeting Update:

7008/08/2024Open
20240808-01API backlog governance

Eric to check with Miranda in Issue #60 if her preference is for separate sub-projects, or for DN to join NSB sub-project

  • No response yet

Meeting Update:

#6008/08/2024Open

Discussion

Current Issues 

17 CentillionNew Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement
The API template is available in PR#386.

Published new standards, Next meeting (this time) Nick will bring all the documentation and present everything putted together

The issue is not eligible to be closed yet.

MEETING UPDATE:

  • Pending to provide a concrete API description into the API proposal template
4

Governance

Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments)
The aim is to update the governing document to reflect on the updated changes on API submission pipeline, according to the new structure of the API backlog table.

Ricardo is currently working on modeling a new table

Struggling with the new Table model.

Bring the PRs from the old repo 

Makes sense to bring the table to confluence? 

GitHub seems to be more accesible and is visited by further people (devs. etc.PR is uploaded: New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog (github.com)

The issue is not eligible to be closed yet.

MEETING UPDATE:

  • Not discussed
23

TelecomsXChange

New Proposal: Carrier Wholesale Pricing
The API template is available in PR#393

First YAML avaliable here

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

ACTION: Ricardo to reach up TelecomXchange to see if the could connect next meetings

MEETING UPDATE:

  • Not discussed
24

Netfocusin Technologies

New Proposal: Steering of Roaming Management
The API template is available in PR#398


Does not seem to be in the Scope of Camara. 

Not an east-west (not between telcos) Already included in 3GPP as technical viable (provided in comment)

The issue is not eligible to be closed yet.

ACTION: Check for support/commitment from the partners (technical implementation approach important)

Meeting Update:

  • No update

35

China Mobile

5G New Calling

The API template is available PR#31

Not treated

Telefonica and Vodafone willing to see the presentation to check whether there is support for this

To be treated in next session (still pending for providing extra info)

Pending to clarify scope with VerifedCaller

MEETING UPDATE:

  • Not discussed

41

Telefonica

New API Proposal: Telco Scoring

The API template is available #42

Input from OGW Drop 4

Presented slides: API-Overview-TelcoScore.pptx

The API seems to not fit within KYC and new sg should be created. Support is required, feel free

Scoring can be calculated both with any user registered in the telco. Less information means less scoring, Algorithm may be different for each of the implementators (MNO)

ACTION: Toshi validate if This APImay fit within KYC API familiy → The issue was rised but still under discussion →(Toshi's proposal 20240627) In API Backlog 20240613 meeting, Jorge TEF and Toshi KDDI agreed that the API does not fit within the existing KYC-SP.  Then, in KYC-SP 20240625 meeting, that was shared within KYC -SP and there was no objection.  Closed.

Pending meeting with DT to seek for support.

ACTION Noel to come back to TEF

MEETING UPDATE:

  • Not discussed

50

Verizon

Device Management

The API template is available #30

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

MEETING UPDATE:

  • Not discussed

60

Ericsson

New API proposal-Dedicated Networks

The API template is available #59

Thorsten presented the proposal: Material here

Image Removed

There have been a similar work in a TMF API. Pierre offere himself to Thorsten to reach up

DECISION New repo/subproject to be created and a family that groups both NSB and DN

ACTION Telefonica providing comments this afternoon and moving to TSC → Action complete

MEETING UPDATE:

    • Comments from TEF addressed in Issue #60
    • ACTION: Eric to check with Miranda in Issue #60 if her preference is for separate sub-projects, or for DN to join NSB sub-project

NOTE: Can be taken to TSC if agreement by end of Thursday 

61

Vodafone

Scope Enhancement for Network info

Seems that Connectivity Insigts is more suitable as there is already work done in the Device Status regarding connection status. 

As there is more alike a device centric information maybe fits better in device status. 

Connectivity insights is more focused in the network status

As it could be used in both of the contexts a new API may be the best option. 

DECISION: There is not such a big change for DS subproject so scope could be enhanced and new repo created within the same Device status family

ACTION: Create the template in a PR related to 66 → Fixed

API familiy → The issue was rised but still under discussion 

→(Toshi's proposal 20240627) In API Backlog 20240613 meeting, Jorge TEF and Toshi KDDI agreed that the API does not fit within the existing KYC-SP.  Then, in KYC-SP 20240625 meeting, that was shared within KYC-SP and there was no objection.  Closed.

Pending meeting with DT to seek for support.

ACTION Noel to come back to TEF

MEETING UPDATE:

  • Not discussed

50

Verizon

Device Management

The API template is available #30

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

MEETING UPDATE:

  • AP: contact Verizon to ensure participation in next backlog meeting

60

Ericsson

New API proposal-Dedicated Networks

The API template is available #59

Thorsten presented the proposal: Material here

Image Added

There have been a similar work in a TMF API. Pierre offere himself to Thorsten to reach up

DECISION New repo/subproject to be created and a family that groups both NSB and DN

ACTION Telefonica providing comments this afternoon and moving to TSC → Action complete

Comments from TEF addressed in Issue #60

ACTION: Eric to check with Miranda in Issue #60 if her preference is for separate sub-projects, or for DN to join NSB sub-project

No response regarding this

MEETING UPDATE: pending to confirm eric's comments in Issue #60


61

Vodafone

Scope Enhancement for Network info


To clarify if new API is proposed  in the Device Status Family or it's an enhancement over an existing API.

To clarify its relationship with Open Gateway Telco Finder API .MEETING UPDATE:→ 

Kevin opened PR #72 to complement Issue #66. Both still open.

Noel commented that this is likely to be accepted

New repository is likely to be required

NOTE: Can be taken to TSC if agreement by end of Thursday 

Comments have been provided in the issue

MEETING UPDATE: Device Status group to confirm, TSC will review the match or alignment with Telco finder (GSMA)

 

63

MTN

New API proposal - IMEI Fraud

The API template is available #64

This API was presented already and included in an existing group but no work was done so discontinued. Now Rebecca is presenting the proposal seeking for support

DeviceCheck GSMA proposal overlaps thisACTION Chenosis Check the material shared by Eric/GSMA regarding DeviceCheck

VDF propose to include it under Device Identifier group, to be validated by Chenosis/MTN

MEETING UPDATE:

IMEI Fraud will offer more information to developers than GSMA Device Check service.

MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense.

Request for meeting already sent by GSMA to MTN

Outcome of meeting awaited before deciding if this API proposal should proceed in CAMARA

NOTE: Can be taken to TSC if agreement by end of Thursday MEETING UPDATE:

  • Pending to be confirmed by MTN, AP to be raised.

 

68

Telefonica

New API proposal - Consent URL

The API template is available #67

The API proposal was presented, including additional slide info 

Discussion to follow offline in the issue/PR.

MEETING UPDATE:

Not discussed

Discussion to follow offline in the issue/PR.

MEETING UPDATE:

  • To hold a separated ad-hoc meeting to clarify the scope and need of the API (conclusions to be shared with backlog before any further decision)


70

Cablelabs

New API proposal - Quality by Design

The API template is available #71

Slides available here: here
YAML available here: here

New API being proposed to allow 3rd party applications to interact with the access network.

ACTION Clarification pending on the differences with current Mobile/Fixed QoD and Network info / Quality indicator APis

MEETING UPDATE:

Proposal is that QbD be a scope enhancement to Connectivity Insights

Will likely require new API, hence new repository required

QdD supporters will attend Connectivity Insights meeting next week to finalise proposal

Awaiting outcome of

Connectivity Insights meeting before finalising if new repository required

NOTE: Can be taken to TSC if agreement by end of Thursday Connectivity Insights meeting before finalising if new repository required

MEETING UPDATE:

  • New repo to be created (new separated API) but included into the existing Connectivity insights family. To be confirmed base on the last meeting minutes. As soon as clarified, it will be included in next TSC.


20

Deutsche Telekom

Best Interconnection
The API template is available in PR#381
Input from OGW Drop 3

Seek for support

ACTION: See if there is any overlap within EdgeCloud

ACTION: Nick (centillion) to review with Noel (DT) about the match of use cases and consider support.

MEETING UPDATE:

DECISION API to be de-prioritised following de-prioritisation by OGW, but to remain in backlog. Issue to remain open.

MEETING UPDATE:

  • Not discussed, waiting for support


Closing Issues

22

T-Mobile US

Capability and Runtime Restrictions
The API template is available in PR#384

It was accepted by the TSC to treat this as a new API

Initial YAML files to be included in the API TEMPLATE

MEETING UPDATE:

  • Not discussedClarifications will be provided by Murat.
18TotogiNew Proposal: Receive SMS
The API template is available in PR#391

Seems to fit in the SMS as a new scope enhancement 

The issue is not eligible to be closed yet.

ACTION: Ricardo to formaly proceed with the scope enhancement os the SMS group

MEETING UPDATE:

  • Not discussed
19

Deutsche Telekom

New Proposal: Device Quality Indicator
The API template is available in PR#380
Input from OGW Drop 3

Noel proposed Device Status subgroup to integrate their APIs within Noel's. Noel to make the proposal to the API Backlog and provide update

Two proposals Issue 19 and 28 would be integrating within the Device Status subproject The subgroup people is okay with this

The issue is not eligible to be closed yet.

Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue, Vodafone commited and a third supporter is being queried) Both issue 19  and 28 to the DeviceStatus family and separate repositories (deviceStatus) →  Device Quality Indicator

DECISION formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status)

DECISION There is agreement Orange, DT and VDF, next backlog meeting there should be the outcome for this issue

Pending to confirm codeowner/maintainers for repo creation, email sent

MEETING UPDATE:

  • All actions complete
  • Issue #19 to be closed. PR #57 already merged.
  • Old Working Groups PR #414 to closed

28

Deutsche Telekom

New API Proposal: Device Data Volume

New template in PR#39

Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue) Both issue 19  and 28 to the DeviceStatus family and separate repositories (deviceStatus) → Device Data Volume

DECISION formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status)

DECISION There is agreement Vonage, DT and VDF, next backlog meeting there should be the outcome for this issue

Pending to confirm codeowner/maintainers for repo creation, email sent

MEETING UPDATE:

  • All actions complete
  • Issue #28 to be closed. PR #39 already merged.

34

China Unicom

New API Proposal: Shutdown ServiceStatus (SubscriptionStatus)

The API tempate is available in PR#32

DECISION  Separate Repos should be created but same familiy (KYC) in order to have coordination meeting

Pending to confirm codeowner/maintainers for repo creation, email sent

MEETING INVITE:Included in today's TSC approval.

  • Issue #34 can be closed and PR #32 merged

Closed Issues

20
Issue

Owner

API

Repository

53

API Backlog

Scope Enhancement Template

The API template is available #52

N/A

54

KDDI

Number Recycling

The API template is available 55

DP #

DP description

Related issue

20240711-01

Formal agreement from the Device Status subgroup is required for Device Data Volume and Device Quality indicator. To be decided in next API Backlog Meeting

19 28

20240711-02

Shutdown Service: Separate Repos should be created but same family (KYC) in order to have coordination meeting

34

20240711-03

Number recycling has enough support, move to TSC. Proposal is to be in the same KyC family but separate repos

54
20240711-04

Dedicated Networks: Proposal is to have separate repos/subproject yet, this needs to be addressed

60
20240808-01

Best Interconnection API to be de-prioritised following de-prioritisation by OGW, but to remain in backlog. Issue to remain open.

NumberRecycling

45

Telefonica

Scope Enhancement: KYC-Match API -Scoring logic 

The API template is available #46

KYC-Match

Decision Points

Pending Codeowners and maintainers (requested in comment)

Action Points

AP #

AP Owner

AP description

Related issue

Due date

Status

 

 

 

 

 

 

Decision Points

DP #

DP description

Related issue
















AoB

Next Backlog conf. call: 22nd August, 15-1612th September, 10-11 UTC+2.

Next TSC conf. call:22nd August, 16:30 UTC+2

Q&A

How does CAMARA API pipeline work?

...