Versions Compared

Key

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

...

...

...

Attendees

 

Organization

Name

Orange

Charter Communications

Christopher Aubut

CableLabs

Telefonica

Alberto Ramos Monaga violeta.gonzalezfernandez@telefonica.com

Vodafone

Ericsson

AT&T

Pierre Close

T-Mobile US

KDDI

Slagen

Nokia

China Telecom

@moyaun Sun

ZTE

KPN

GSMA

Reg Cox

Centilion

Chunghwa Telecom

Deutsche Telekom

Noel Wirzius

MTN

China Mobile

Verizon

Mahesh Chapalamadugu

PlektonLabs

TIM

fabrizio moggio

NTT

...

  • GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3/4 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress. 

    • Best Interconnect

    • IMEI Fraud API

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.

...

AP #

AP Owner

AP description

Related issue

Status

20240523-01

API Backlog Governance

Backlog Governance to reach up TelecomXchange & Netfocusin to see if the could connect next meetings

23 24

Open

20240711-04

MTN/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: Waiting for more updates, any other operator open to join

63

Open

20240926-03

China Mobile

5G New Calling

35

Open

20241010-02

ALL

IMEI Fraud

  • Provide support from any company to take this API.

63

Open

20241024-02

Verizon

Device Management

  • Slides presented by Mahesh Chapalamadugu & @joshua

    Slide will be uploaded and reviewed offline before approval

50

Open

20241128-01

China Telecom

IoT SIM Status Mgmt API:

Slides presented in the meeting (to be updated into the API proposal documentation)

Eric Murray G. Murat Karabulut New proposal focused on the management of services of devices (activate/deactivate) but still in relation with Device Management concept

Mahesh Chapalamadugu (Verizon) to confirm if both proposals may still be merged

AP: Email thread to be opened to provide a common position

95

Open

20241128-02

China Telecom

IoT SIM Fraud Prevention API

New proposal shared byMoyuan Sun about SIM-Device binding change (possibly related to Device Swap) and area alerting (possibly related to Geofencing). Actions over lines are part of Device Management.

AP: China Telecom to update proposal in PR#103

96

Open

2024112820250109-0401

China Mobile

Facial Recognition

Eric Murray proposes in 126 to consider this APi as part of already existing ModelAsA Service APi group (also from China Mobile)

YinMing Fu considers APi separated as MaaS focused on LLM models

Eric Murray raises issues on match with CAMARA authentication, privacy and identity existing mechanisms to be applied in this API

Jorge Garcia Hospital raised question on the telco capabilities been leveraged, to be clarified

AP to China Mobile to clarify open points

126

Closed

20241128-05

TIM

IoT Data Transfer Activation

Kevin Smith posible overlap with Dedicated Network API (proposal), related to configure a network for a set of devices. To be reviewed.

AP: Open issue in Dedicated Network API to discuss.

143

Closed

20241212-01

KDDI

QoS Booking

Open issue in Dedicated Network API to discuss possible overlap.

154

Closed

20250109-01

TIM

IoT Data Transfer Activation

Modify current API proposal (PR and name) with new use cases (TIM)

143

TIM

IoT Data Transfer Activation

Modify current API proposal (PR and name) with new use cases (TIM)

143

Open

20250123-01

Verizon/China Telecom

Device Management & IoT SIM Status Mgmt API

Agree on next steps, Mahesh Chapalamadugu to confirm way forward e.g. mix both API proposals

50 95

Open

20250123-02

China Telecom

IoT SIM Fraud Prevention API

Consider merging in previous APIs or requesting it’s access in other group.

95

Open

20250123-03

TEF/DT

Dynamic Connectivity Data

Modify current API proposal according to comments.

163

Open

20250123-04

ALL

Traffic Influence API - Sandbox repository

Confirm inclusion of Traffic Influence API new repository (offline approval if no against comments are received)

169

Open

Decision Points

DP #

DP description

Status

1

Increase backlog meeting duration from 1 to 1:30:

  1. 2nd Thursday of the month (10-11:30 CET)

  2. 4th Thursday of the month (15-16:30 CET)

Agreed

 2

 Move meeting schedule to UTC:

  • Backlog 2nd Thursday: 09:00 UTC (10:00 CET / 01:00 PT) [Note: during next DST, 11:00 CEST / 02:00 PST]

  • Backlog 4th Thursday: 14:00 UTC (15:00 CET / 06:00 PT) [Note: during next DST, 16:00 CEST / 07:00 PST]

Or align with TSC:

  • Backlog 2nd Thursday: 09:00 UTC (10:00 CET / 01:00 PT) [Note: during next DST, 11:00 CEST / 02:00 PST]

  • Backlog 4th Thursday: 15:00 UTC (16:00 CET / 07:00 PT) [Note: during next DST, 17:00 CEST / 08:00 PST]

Agreed

 3

 As in APIBacklog/issues/123 , companies see a suitable feature to have a spot in each repository where participants can be reported, stating the interest of those participant companies for this API.

Decision based on TSC feedback:

  • Create a participants / interested parties template to be included in each confluence page. Company names to be included.

    • Create a description of the meaning of participant (companies interested in an API, participating actively or passively in the WG…)

    • Templates to be provided and included in current and new WG

Agreed

 

 

 

 

...