Versions Compared

Old Version 1

changes.mady.by.user Jose Ordonez-Lucena

Saved on

compared with

New Version 2

changes.mady.by.user Jose Ordonez-Lucena

Saved on

Key

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


DRAFT

Attendees


AT&T Pierre Close
CableLabsRandy Levensalor
Charter CommunicationsChris Aubut, Justin Pace, Jason Page
Deutsche TelekomNoel Wirzius
EricssonJan Friman
InfosysChintan Lodariya
HuaweiZhang Kai
NokiaTanja De Groot
Telecom ItaliaFabrizio Moggio
TelefónicaJose Ordonez-Lucena, Jorge García Hospital
VodafoneEric Murray, Kevin Smith


Agenda Proposal

  • Antitrust Policy
  • Approval of minutes of last conf. call
  • Recent Updates & Recap
  • Review of Action Points
  • Discussion
    • OGW Drop 3 APIs: 336, 375, 376
    • Other APIs: 351, 372, 378
    • Governance: 367
  • Action Points
  • 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 LF.


Image Modified

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
    • 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: The minutes are xxxxx.

Recent Updates & Recap

Technical Steering Committee (TSC)

  • Last TSC call held on Feb 1st. Minutes available here.
  • "Network Slicing" API proposal
  • "Call Forwarding Signal" API proposal
  • "Device Visit Location" API proposal
    • Discussion held, with a proposed way forward captured: 
      • GSMA OGW product workstream to re-check commercial value of such an API
      • Anti-fraud use case to be reviewed and clarified
      • Remove marketing use case
      • TSC to then agree disclaimer to be included in sub-project repository.
    • Issue 330 will be eligible to be closed after TSC approval.

Backlog table

Review of Action Points

AP #

AP Owner

AP description

Related issue

Due date

Status

20230125-06

Charter Communications

To submit the deck here, and link it to the issue. 

378

2024/02/01

Open

Closed

20230125-05

Deutsche Telekom

to improve and clarify the API proposal, based on discussion during the call.

376

2024/02/01

Open

20230125-04

Deutsche Telekom

to improve and clarify the API proposal, based on discussion during the call.

375

2024/02/01

Open

20230125-03

Telecom Italia

to seek codeowners/maintainers from Orange and China Unicom. 

3592024/02/07

Closed

20230125-02TelefónicaTo send out information to TSC, asking for API approval. 3592024/01/25Closed
20230125-01TelefónicaTo inform TSC on the decision of Sub-Project name, so that CAMARA admin can proceed with the repo creation3172024/01/25Closed
20240111-04TelefónicaOpen a new PR to update governing document for API submission pipeline3672024/02/15Open


Discussion

Current Issues 

330China UnicomNew API proposal: Device Visit Location
The API template is available in PR#329

The issue was discussed in last TSC call (minutes available here). 

Discussion held, with a proposed way forward captured: 

    • GSMA OGW product workstream to re-check commercial value of such an API
    • Anti-fraud use case to be reviewed and clarified
    • Remove marketing use case
    • TSC to then agree disclaimer to be included in sub-project repository.

The issue is not eligible to be closed yet.

336TelefónicaNew API proposal: OGW Home Location Verification
The API template is available in PR#337.
Input from OGW Drop 3
  • Telefonica: we are progressing on step 1 and 2. 
  • TIM: interested in participating in the API (no commitment yet to becoming support).

The issue is not eligible to be closed yet.

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

No delegate from Centillion attended. The issue was not treated in this conf. call. 

The issue is not eligible to be closed yet.

367

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.

The issue was not treated in this conference call. No progress. 

The issue is not eligible to be closed yet.

372
New Proposal: Receive SMS
No PR available.

The issue was not treated in this conference call.

The issue is not eligible to be closed yet.

375

Deutsche Telekom

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

  • DT presented the template, together with some supporting slides. 
  • DT clarified that it is similar to "connectivity insights", but more focus on device side. 
  • Ericsson: the naming is "device", but the input data also covers network and historical data.
  • Vodafone: the API produces relative quality levels (e.g., low, medium,...) without giving any specific quantitative information/KPIs. How many quality levels do you expect to define?
    • DT: 3 (as traffic lights) or even 5. Open for discussion.
  • DT noted the input params for first version. 
    • Telefónica: some input params seem to be output params of other ongoing APIs (e.g., connectivityInsights,...). Is there a need for operator to implement these ongoing APIs for offering the new API proposal? Or is it just a recommendation
    • DT clarified it is just a recommendation. 

ACTION: to improve and clarify the API proposal, based on discussion during the call.

The issue is not eligible to be closed yet.

376

Deutsche Telekom

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

  • DT presented the template, together with some supporting slides. 
  • Telefónica asked whether this API proposal is focused/limited to edge, and possible relationship with EdgeCloud repo. 
    • DT: EdgeCloud more focused on cloud nodes, whereas this API proposal focuses on interconnection point. Vodafone agrees.
  • Telefónica: what about relationship with traffic influence API?
    • DT: needs to double check when traffic goes / does not go to the Internet.
    • TIM: The traffic influence is very much mobile oriented. 
  • Telefónica: more info on API input/out params? Is there a plan to standardise the algorithm/formula for API logic, and how to process inputs on links/hops?
    • DT will provide further info. 

ACTION: to improve and clarify the API proposal, based on discussion during the call.

The issue is not eligible to be closed yet.

378

Charter Communications

CPE management
The API template is available in PR#379.       First YAML available here.

Charter Communications presented a slide deck to elaborate on API proposal. There was no time to really discuss the topic, since we ran out of time . We will resume the discussion next call. 

ACTION: to submit the deck here, and link it to the issue. 

The issue is not eligible to be closed yet.

Closed Issues

317

China Unicom

New Proposal: Network Slicing API
The API template is available in PR#333


The repo is available → https://github.com/camaraproject/NetworkSliceBooking

359Telecom Italia

New API proposal: Call Forwarding Signal
The API template is available in PR#361.     Input from OGW Drop 3

The repo is available → https://github.com/camaraproject/CallForwardingSignal

New Issues


Action Points

AP #

AP Owner

AP description

Related issue

Due date

Status

20230125-06

Charter Communications

To submit the deck here, and link it to the issue. 

378

2024/02/01

Open

20230125-05

Deutsche Telekom

to improve and clarify the API proposal, based on discussion during the call.

376

2024/02/01

Open

20230125-04

Deutsche Telekom

to improve and clarify the API proposal, based on discussion during the call.

375

2024/02/01

Open

20230125-03

Telecom Italia

to seek codeowners/maintainers from Orange and China Unicom. 

3592024/02/07

Closed

20230125-02TelefónicaTo send out information to TSC, asking for API approval. 3592024/01/25Closed
20230125-01TelefónicaTo inform TSC on the decision of Sub-Project name, so that CAMARA admin can proceed with the repo creation3172024/01/25Closed
20240111-04TelefónicaOpen a new PR to update governing document for API submission pipeline3672024/02/15Open

Decision Points

DP #

DP description

Related issue

xxxx

xxxx

359

xxxxx

"xxxxx



AoB

Next conf. call: 22nd February, 15-16 CET.


Q&A

How does CAMARA API pipeline work?

...