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:

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

Recommendation is that China Mobile join regular WebRTC call to discuss 5G New Calling proposal there.

MEETING UPDATE:

No updates

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:

Review match with other Device management APIs (home devices or similar) and IoT/Device status (AP Backlog: contact Mahesh)

Also ensure this is a proper telco capacity to be consumed by developers, in comparison with Operate API (TM Forum) that are related to Aggregators.

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)

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

Moyuan Sun proposal to be modified to “communication capabilities” to avoid overlap with Device Management API proposal 50

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

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

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

MEETING UPDATE:

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.

China Telecom updates proposal in PR#103, keep offline discussion around Device Management.

109

Verizon

Support application resource requirements in application profiles

The API template is available in PR#110

METING UPDATE:

No update

115

China Unicom

SIM Historical Information

The API template is available in PR#114

Eric Murray comment: 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

METING UPDATE:

no updates

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

METING UPDATE:

no updates

122

China Unicom

Number Of Cards Under User's ID

The API template is available in PR#119

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

METING UPDATE:

no updates

126127

China MobileFacial RecognitionUnicom

Network Health Assessment

The API template is available in PR#130PR#129

EasyCLA to be solved

METING UPDATE:

material presented by YinMing Fu.

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

--> MNO face database is used

AP to China Mobile to clarify open points

METING UPDATE:

To modify the template to ScopeEnhancement of MaaS.

YinMing Fu updated  PR#130 and API will be treated in next TSC 19th dec. 15:00 UTC

127

China Unicom

Network Health AssessmentNo updates

128

China Unicom

Network Traffic Analysis

The API template is available in PR#129

EasyCLA to be solved

METING UPDATE:

No updates

136

China Unicom

eSIM Remote Management

The API template is available in PR#129EasyCLA to be solvedPR#140

METING UPDATE:

No updates

128143

China Unicom

Network Traffic AnalysisTIM

IoT Data Transfer Activation

The API template is available in PR#129EasyCLA to be solvedPR#144

Focused on booking resources for a non-warranted connection for IoT, group of many devices at once, during a certain period. Not directly related to QoD or HighThroughput API.

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

METING UPDATE:

No updates

136

China Unicom

eSIM Remote ManagementIssue#14 raised to discuss about posible overlap

fabrizio moggio : Proposal to include IoT API (separate repo) as part of the Dedicated Network “family” (share participants and meetings) to align use cases and definitions.

Jan Friman : this API looks like a specialization of Dedicated network API

Proposal: To be proposed in the Dedicated network issue to validate Issue#14

154

KDDI

QoS Booking

The API template is available in PR#140PR#155

143

TIM

METING UPDATE:

No updates

141

TIM

Energy Footprint Notification

The API template is available in PR#142

API to report energy consumption of a service including computing and communication.

Kevin Smith asks about the “energy scopes” managed by this API (carbon footprint, electricity consumption…)

https://datatracker.ietf.org/group/green/documents/

fabrizio moggio proposes to create an API that can report reports from the operator depending on the calculation that each telco can create (depending on the information sources of each one).

Nick Venezia https://taxation-customs.ec.europa.eu/carbon-border-adjustment-mechanism_en#:~:text=Why%20CBAM?-,CBAM,the%20decarbonisation%20of%20EU%20industry

METING UPDATE:

Jan Friman is the notification raised before the service or after?

fabrizio moggio is raised during the service consumption, not a prediction

Proposal: API to be proposed to next TSC 19th dec. 15:00 UTC

IoT Data Transfer ActivationSlide deck

Jorge Garcia Hospital TEF supports this API.

Q: Will this API be a new repo or a new API of QoD repo?

Tanja de Groot Could QoS booking API be considered as another "variant" of the Dedicated Networks API?

Masaharu Hattori: Dedicated Network is focused on booking network resources, while QoD booking is related to book a quality session, independent to specific resources. Dev schedules just a QoD session to fulfill a required profile.

Jan Friman Dedicated Networks is handling this use cases of booking resources to fill the needs of an app, closely related to this proposal

Eric Murray proposal inherits from QoD API, but may consider a sue case overlap as booking resources.

To discuss in Dedicated Network (Monday 16th 9UTC)

157

China Unicom

Voice Notification

The API template is available in PR#158

METING UPDATE:

160

China Unicom

Voice Verification Code

The API template is available in PR#161

METING UPDATE:

163

Telefonica

Dynamic Connectivity Data

The API template is available in PR#164

METING UPDATE:

Issue #

Company

Summary

Status Update

22

T-Mobile US

Capability and Runtime Restrictions

The API template is available in PR#74

Approved for Sandbox repository

Follow-up on API onboarding:

https://github.com/camaraproject/APIBacklog/issues/134

18

Totogi

New Proposal: Receive SMS

Issue #

Company

Summary

Status Update

22

T-Mobile US

Approved for Sandbox repository

Follow-up on API onboarding:

https://github.com/camaraproject/APIBacklog/issues/134

18

Totogi

• 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

20

Deutsche Telekom

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

91

Telefonica

Fixed Lines in Location

The API template is available in PR#92

METING UPDATE:

Issue open in Carrier Billing https://github.com/camaraproject/CarrierBillingCheckOut/issues/190

93

Telefonica

Line Eligibility for Carrier Billing API

The API template is available in PR#94

89

China Mobile

IP High-throughput Elastic Network 

The API template is available in PR#90

Approved for Sandbox repository

Follow-up on API onboarding:

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

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

91

Telefonica

Fixed Lines in Location

The API template is available in PR#92

METING UPDATE:

Issue open in Carrier Billing https://github.com/camaraproject/CarrierBillingCheckOut/issues/190

93

Telefonica

Line Eligibility for Carrier Billing API

The API template is available in PR#94

MEETING UPDATE:

Issue open in location https://github.com/camaraproject/DeviceLocation/issues/271

89

China Mobile

IP High-throughput Elastic Network 

The API template is available in PR#90

Approved for Sandbox repository

Follow-up on API onboarding:

126

China Mobile

Facial Recognition

The API template is available in PR#130

EasyCLA to be solved

METING UPDATE:

material presented by YinMing Fu.

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

--> MNO face database is used

AP to China Mobile to clarify open points

METING UPDATE:

To modify the template to ScopeEnhancement of MaaS.

YinMing Fu updated  PR#130 and API will be treated in next TSC 19th dec. 15:00 UTC

141

TIM

Energy Footprint Notification

The API template is available in PR#142

API to report energy consumption of a service including computing and communication.

Kevin Smith asks about the “energy scopes” managed by this API (carbon footprint, electricity consumption…)

https://datatracker.ietf.org/group/green/documents/

fabrizio moggio proposes to create an API that can report reports from the operator depending on the calculation that each telco can create (depending on the information sources of each one).

Nick Venezia https://taxation-customs.ec.europa.eu/carbon-border-adjustment-mechanism_en#:~:text=Why%20CBAM?-,CBAM,the%20decarbonisation%20of%20EU%20industry

METING UPDATE:

Jan Friman is the notification raised before the service or after?

fabrizio moggio is raised during the service consumption, not a prediction

Proposal: API to be proposed to next TSC 19th dec. 15:00 UTC