Page Comparison

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:Nick Venezia : Framework proposal including different APIs that may interact with existing ecosystem. Pending to provide info, work expected to be started in 1Q25

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:

Not treatedNo 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:

Not treatedNo 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 modifications

Decision: China Mobile to update proposal in github with proposed modifications. If done quickly, proposal can be taken to TSC meeting on Thursday 21st.

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 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 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:

109

Verizon

Support application resource requirements in application profiles

The API template is available in PR#110

METING 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

METING UPDATE:

122

China Unicom

Number Of Cards Under User's ID

The API template is available in PR#119

METING UPDATE: