Page Comparison

DRAFT MINUTES

Attendees

Organization	Name
Orange	Ludovic Robert
Charter Communications	Christopher Aubut
CableLabs
Telefonica
Vodafone	Eric Murray
Ericsson	Jan Friman
AT&T	Pierre Close
T-Mobile US
KDDI
Slagen
Nokia
China Telecom
ZTE
KPN
GSMA
Centilion
Chunghwa Telecom
Deutsche Telekom
MTN
China Mobile
Verizon
PlektonLabs

...

METING UPDATE:

Issue #	Company	Summary	Status Update
17	Centillion	New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#73.	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. Pending to provide a concrete API description into the API proposal template Action: Clarifying with interested parties whether this may be a possible API or a Framework etc. AP: provide required information and examples MEETING UPDATE: No update
23	TelecomsXChange	New Proposal: Carrier Wholesale Pricing The API template is available in PR#77 First YAML available here	The issue was not treated in this conference call The issue is not eligible to be closed yet. ACTION: Backlog Governance to reach up TelecomXchange to see if the could connect next meetings MEETING UPDATE: No update
24	Netfocusin Technologies	New Proposal: Steering of Roaming Management The API template is available in PR#78	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	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) Presentation of current proposal was shared in the meeting. Slides to be included in PR#31. G. Murat Karabulut asked about the proposal been part of WebRTC enhancement or new API → new API. Eric Murray asked about examples of 3rd parties in this API flow → app invoquing API to request or activate features, which can be enabled or not by the telco. Mark Cornall raised the existance of a 5G New Calling project in GSMA: https://www.gsma.com/get-involved/gsma-foundry/5g-new-calling/ & 5GNCTF Meeting#1 ACTION: Operators open to comment/ask for clarification and support the API. Eric Murray asks for user stories that can explain the behaviour of the proposed API, as not clear how this interacts with the proper 5G New Calling standard and how it solves the features that are proposed. AP for Haojie Li https://github.com/camaraproject/WebRTC/issues/52 to discuss in WebRTC about relationship new information to be uploaded and treated in next session MEETING UPDATE: No-one from China Mobile present. Recommendation is that China Mobile join regular WebRTC call to discuss 5G New Calling proposal there.
50	Verizon	Device Management The API template is available PR#30	The issue was not treated in this conference call The issue is not eligible to be closed yet. Action to contact Verizon to ensure participation in next backlog meeting API proposal presented by Mahesh Chapalamadugu , clarified this proposal is targeted for IoT device management to activate/deactivate/manage the connection of those devices. ACTION:Mahesh Chapalamadugu to upload current yaml for clarification in PR#30, and present again in next meeting. Mahesh Chapalamadugu AP to upload documentation Slides presented by Mahesh Chapalamadugu & @joshua Slide will be uploaded and reviewed offline before approval MEETING UPDATE: No update
63	MTN	New API proposal - IMEI Fraud The API template is available PR#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 this 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 Pending to be confirmed by MTN, AP to be raised. Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. ACTION: Pending from MTN for moving on with this API. Maybe to be included in the Device Identifier family. @reg no further information from MTN, consider to de-prioritize, pending to further update Any other operator open to take the lead of this API is welcomed MEETING UPDATE: No update (pending)
89	China Mobile	IP High-throughput Elastic Network The API template is available in PR#90	Supporting document (presented) https://github.com/camaraproject/APIBacklog/raw/0a447dd4c53d0c675f8d72fc5622ff65eb48f7e3/documentation/SupportingDocuments/APIproposal_IP-high-throughput-elastic-network_ChinaMobile.pptx Jan Friman asked about the relation of this proposal with current CAMARA’s APis dedicated to network config (QoD, slice booking…). @qiuhai explained that this proposal is focused on enabling new network technologies like Srv6 Mark Cornall shared comments about the technology dependence on QoD solutions Kevin Smith & Jorge Garcia Hospital asked for more details on the difference with current proposals Pending review from Kevin about responses in the PR. Jorge Garcia Hospital raised concerns about technology dependancy in this API proposal MEETING UPDATE: Jianfeng Huang presented an update of the proposal. API will now be technology agnostic. Mark Cornall agrees with proposed modificationsDecision: No other objections to modified proposal raised in the meeting AP: China Mobile China Mobile to update proposal in github with proposed modifications. Update should be to both PR#90 and Issue #90. DECISION: If done quicklyupdate is done by end Friday 15 Nov 2024, proposal can be taken put to to TSC meeting on Thursday 21st 21 Nov 2024 for final approval. Otherwise will need to be 05 Dec 2024 meeting.
95	China Telecom	IoT SIM Status Mgmt API The API template is available in PR#105	Relationship with device management proposal, to confirm relationship. AP: China Telecom MEETING UPDATE:	96	China Telecom	IoT SIM Fraud Prevention API The API template is available in PR#103	Jorge Garcia Hospital is it required to create a new Meeting considered that this proposal has some overlap with the Device Management proposal from Verizon APs: China Telecom China Telecom to discuss with Verizon (Mahesh Chapalamadugu) bringing this API into scope of Device Management API proposal. Discuss initially within Issue #50. If scopes can be merged, Verizon can update PR#30 accordingly; Otherwise propose to continue proposal as a new sub-project at next API Backlog meeting
96	China Telecom	IoT SIM Fraud Prevention API The API template is available in PR#103	Jorge Garcia Hospital is it required to create a new set of APIs only for IoT devices or can they live in the existing groups? Eric Murray agrees, device status can take in charge of this new parameters, check first with this subgroup https://github.com/camaraproject/DeviceStatus AP: China Telecom MEETING UPDATE:	97	China Telecom	IoT SMS send API The API template is MEETING UPDATE: Meeting agreed with China Telecom that this proposal does not fit within Device Status sub-project APs: China Telecom China Telecom to discuss with Verizon (Mahesh Chapalamadugu) bringing this API into scope of Device Management API proposal. Discuss initially within Issue #50. If scopes can be merged, Verizon can update PR#30 accordingly; Otherwise propose to continue proposal as a new sub-project at next API Backlog meeting
97	China Telecom	IoT SMS send API The API template is available in PR#104	Jorge Garcia Hospital Mahesh Chapalamadugu requires to validate this proposal with existing SMS Send API https://github.com/camaraproject/ShortMessageService AP: China Telecom MEETING UPDATE: Proposal to be withdrawn
109	Verizon	Support application resource requirements in application profiles The API template is available in PR#110	METING UPDATE: 115No update
115	China Unicom	SIM Historical Information The API template is available in PR#114	METING UPDATE:	121	China Unicom	User Account Spend Count The API template is available in PR#120	122	China Unicom	Number Of Cards Under User's ID The API template is available in PR#119	METING UPDATE:Eric Murray Sounds like a “historical SIM Swap” API. Discuss with SIM Swap sub-project. APs: China Unicom Upload presentation to github by adding as additional document to PR#114 Raise issue in SIM Swap sub-project proposing to bring new use case into SIM Swap. Refer to PR#114 in the new issue. If SIM Swap sub-project agree that new API fits within the scope of that sub-project, then submit a sub-project scope modification request to API backlog, otherwise try to progress proposal as a new sub-project at next API Backlog meeting
121	China Unicom	User Account Spend Count The API template is available in PR#120	METING UPDATE: Use case appears to be a KYC use case APs: China Unicom Upload presentation to github by adding as additional document to PR#120 Raise issue within KYC sub-project proposing to bring new use case into KYC. Refer to PR#120 in the new issue. If KYC sub-project agree that new API fits within the scope of that sub-project, then submit a sub-project scope modification request to API backlog, otherwise try to progress proposal as a new sub-project at next API Backlog meeting
122	China Unicom	Number Of Cards Under User's ID The API template is available in PR#119	METING UPDATE: Use case appears to be a KYC use case APs: China Unicom Upload presentation to github by adding as additional document to PR#119 Raise issue within KYC sub-project proposing to bring new use case into KYC. Refer to PR#119 in the new issue. If KYC sub-project agree that new API fits within the scope of that sub-project, then submit a sub-project scope modification request to API backlog, otherwise try to progress proposal as a new sub-project at next API Backlog meeting

Closing Issues

Issue #

Company

Summary

Status Update

22

T-Mobile US

Capability and Runtime Restrictions

The API template is available in PR#74

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

Initial YAML files to be included in the API TEMPLATE

Clarifications will be provided by Murat.
- Intended to cover these slides but time ran out:
  View file
  name Capabilities_and_Runtime_Restrictions_Update.pptx
  and request ‘sandbox creation’. Will update the Issue #22 accordingly.
To be reviewed in TSC on 17th

MEETING UPDATE:

TSC Decision: Ask to G. Murat Karabulut to provide some examples where this API will be useful. To be revisited during the after-next TSC meeting14 Nov 2024 .

18

Totogi

New Proposal: Receive SMS

The API template is available in PR#75

20240327-02 was completed. Herbert responded but not the subgroup owners, no activity seems to had happened for a month: Issue #9 · camaraproject/ShortMessageService

Seems to fit in the SMS as a new scope enhancement

The issue is not eligible to be closed yet.

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

MEETING UPDATE:

Reminder sent

41

Telefonica

New API Proposal: Telco Scoring

The API template is available PR#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 API may fit within KYC API family → The issue was raised 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

Telefonica manage to find the support of VDF (Kevin confirmed in the chat also) and DT if no objections. The name should be readressed, Jorge was prposing Telco Index to avoid using legal restrictions for using words "Credit" and "Scoring".

Nick propose Telco Trust → Discussing this in the issue ofline.

Tanja (note in chat on behalf of Release Mgmt): Reminder to not use Telco specific terms in API names. To avoid: Telco, operator, CSP, subscriber, customer, EMEI, UE, etc.

Pending:

Group created, pending to include maintainers/codeowners

MEETING UPDATE:

All ready, to be closed

20

Deutsche Telekom

Best Interconnection

The API template is available in PR#88

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.

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

MEETING UPDATE:

Not treated

68

Telefonica

New API proposal - Consent URL

The API template is available PR#67

The API proposal was presented, including additional slide info

Discussion to follow offline in the issue/PR.

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)

Huub Appelboom supports API proposal

G. Murat Karabulut previously raised some concerns but seem clarified with last documentation. (uploaded in API PR#67 and also direct link)

Pending: Proposal to be brought to TSC if no other concern is raised before end of week.

MEETING UPDATE:

under discussion in I&CM

83

China Mobile

Model As A Service Family

The API template is available in PR#84 - MaaS (Model As A Service) Family

China Mobile presented the API

ACTION: To include support from ZTE and Huawei. Proposals in good shape for been moved to TSC approval, Haojie Li asked for one additional round for more clarifications and comments.

MEETING UPDATE:

Group created, actions pending to be solved