Issue #

17 

Centillion

New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement

The API template is available in PR#73.

INITIAL CONTEXT:

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

LAST UPDATES: No response since October 8, 2024.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

23

TelecomsXChange

New Proposal: Carrier Wholesale Pricing

The API template is available in PR#77

First YAML available here

INITIAL CONTEXT:

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

LAST UPDATES: No response for 6 months.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

24

Netfocusin Technologies

New Proposal: Steering of Roaming Management

The API template is available in PR#78

INITIAL CONTEXT:

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)

LAST UPDATES: No response since May 10, 2024.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

35

China Mobile

5G New Calling

The API template is available PR#31

INITIAL CONTEXT:

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.

LAST UPDATES: No response since June 11, 2024.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

63

MTN

New API proposal - IMEI Fraud

The API template is available PR#64

INITIAL CONTEXT:

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

LAST UPDATES: No response since September 6, 2024.

Feb 27, 2025: no treated

MEETING UPDATE:

Mar 13, 2025:

115

China Unicom

SIM Historical Information

The API template is available in PR#114

INITIAL CONTEXT:

@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

LAST UPDATES:

Feb 13, 2025: @Fan Yang to review issue offline and provide feedback and current status of the proposal.

Feb 27, 2025: @Fan Yang no updates, will be reviewed in next meeting

MEETING UPDATE:

Mar 13, 2025:

121

China Unicom

User Account Spend Count

The API template is available in PR#120

INITIAL CONTEXT:

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

LAST UPDATES:

Feb 13, 2025: @Fan Yang to review issue offline and provide feedback and current status of the proposal.

Feb 27, 2025: @Fan Yang no updates, will receive new in next meeting

MEETING UPDATE:

Mar 13, 2025:

122

China Unicom

Number Of Cards Under User's ID

The API template is available in PR#119

INITIAL CONTEXT:

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

LAST UPDATES:

Feb 13, 2025: For 115, 121, 122 information will be uploaded by @Fan Yang , issues to confirm with SIM Swap and KYC subprojects will be raised

Feb 27, 2025: @Fan Yang no updates, news comming in next meeting

MEETING UPDATE:

Mar 13, 2025:

136

China Unicom

eSIM Remote Management

The API template is available in PR#140

INITIAL CONTEXT:

Action for all China Unicom Topics: @Reg.cox will ask for an update from China Unicom in the next meeting

LAST UPDATES:

Feb 13, 2025:@Jan Friman some sequence diagrams will be good to understand the API proposal.

AP: China unicom to upload additional information and flows of the API proposal.

Feb 27, 2025:

• feedback received in https://github.com/camaraproject/APIBacklog/pull/140#issuecomment-2684562782 .

• @Jorge Garcia Hospital need more information on the IF6 interface, whether this API is as well needed to be specified as a MNO interface to the app.

• @Tanja de Groot only for eSIM? yes, only eSIM profiles can be modified with this solution. Question about restricting the terminology, open for next meeting.

MEETING UPDATE:

Mar 13, 2025: @He Dongsheng only IF1 will be standardize in CAMARA.

@Eric Murray : only IoT eSIMs are considered?

Q: any use case regarding eSIM is considered, including travel eSIM or other use cases.

@Tanja de Groot : clean APi template language: please take care in desciptions to avoid references to "telco". Use API provider instead → API template to be fixed

Conclusion: ready for TSC approval to move forward with sandbox

157

China Unicom

Voice Notification

The API template is available in PR#158

LAST UPDATES:

Feb 13, 2025: not treated

Feb 27, 2025:

• proposal presented by @jincui, use cases related to notification launch over IMS channel for callers in device to receive and reach messaged (audio, text)

• @Jorge Garcia Hospital comment raised about the similarity or match with 5G new calling API proposal as targeted for applications to take advantage of the IMS network and callers. AP: To check PR#31

METING UPDATE:

Mar 13, 2025:

160

China Unicom

Voice Verification Code

The API template is available in PR#161

LAST UPDATES:

Feb 13, 2025: not treated

Feb 27, 2025:

• proposal presented by @jincui, use case is focused on using the voice channel to send verification codes instead of by SMS.

• @Jorge Garcia Hospital comment raised about the similarity or match with 5G new calling API proposal as targeted for applications to take advantage of the IMS network and callers. AP: To check PR#31

• AP: for 157 &160 reach offline with china mobile to understand matching between APIs.

MEETING UPDATE:

Mar 13, 2025:

167

Cellcard

IdentityAndConsentManagement

The API template is available in PR#166

LAST UPDATES:

Feb 13, 2025: not treated

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

Issue #

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

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 location https://github.com/camaraproject/DeviceLocation/issues/271

93

Telefonica

Line Eligibility for Carrier Billing API

The API template is available in PR#94

MEETING UPDATE:

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

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:

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

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

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

METING UPDATE:

Approved, pending to decide whether it will be part of same repo or different from MaaS

141

TIM

Energy Footprint Notification

The API template is available in PR#142

Approved:

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

154

KDDI

QoS Booking

The API template is available in PR#155

Slide deck

TSC UPDATE:

QoS booking and current Dedicated Network APIs follow different use cases that need to be handled separately, proposal to create a separate sandbox repo to manage QoS Booking (related to QoD subproject).

METING UPDATE:

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

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

New proposal shared by@Moyuan 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.

Opinion shared, that it could two different YAMLs. Check for TSC.

MEETING UPDATE:

TSC approval for next week, as separate sandbox (one for all the APIs proposed under this issue) as 3 APIs (with different internal features).

109

Verizon

Support application resource requirements in application profiles

The API template is available in PR#110

@Mahesh Chapalamadugu presented this topic, asking for review until the next meeting

METING UPDATE: Aligned with Connectivity Insight, to be confirmed in next TSC

169

TIM

Traffic Influence API - Sandbox repository

https://github.com/camaraproject/EdgeCloud/discussions/313#discussioncomment-11409923

Approve the creation of a separated sandbox repository for Traffic Influence API, now under EdgeCloud repo.

If no objection, tracker will be created accordingly. API and repo will be linked to EdgeCloud subproject.

METING UPDATE:

@fabrizio moggio explained that the Traffic influence API is ready to move into an own sandbox

Agreed

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

@Mahesh Chapalamadugu Action point verify the merge with Device Management for next meeting.

MEETING UPDATE:

Confirmed in:

https://github.com/camaraproject/APIBacklog/issues/50#issuecomment-2642463127

APIs proposals PR to be updated before 17th EoB, and will be brought to TSC approval on 20th.

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

ACTION:

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.

METING UPDATE:

Potential of merging IoT SIM Status Mgmt API in, will be checked by @Mahesh Chapalamadugu until next meeting.

Confirmed in:

https://github.com/camaraproject/APIBacklog/issues/50#issuecomment-2642463127

APIs proposals PR to be updated before 17th EoB, and will be brought to TSC approval on 20th.

163

Telefonica

Dynamic Predictive Connectivity Data

The API template is available in PR#164

LAST UPDATES:

Jan 21, 2025:

• @violeta.gonzalezfernandez@telefonica.compresented the topic, will check if it is going towards connectivity Insights group or QoD

• @Noel Wirzius asked to add for change of the name to bring “Prediction” in, and taking care of ground prediction as well

Feb 13, 2025: not treated

Feb 27, 2025: @Kevin Smith relation to connectivityInsight API in terms of checking connectivity available in the next future, difference is focus on this APis targeted to individual devices. No overlap expected. API to be proposed to TSC.

143

TIM

IoT Network Optimization

The API template is available in PR#144

INITIAL CONTEXT:

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.

LAST UPDATES:

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

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

TIM proposed an alternative approach to complement Dedicated Networks API, so that developer can manage energy modes, IoT slice selection os similar for a IOT device.

@Tanja de Groot @Thorsten Lohmar proposed those features to be generic, not dedicated to IoT use cases

Continue discussion with the new scope, including new API name.

Dedicated network group will still be used to include the previous scope (scheduling a network config for IoT)

New scope of API will be discussed separately.

AP: modify current API proposal (PR and name) with new use cases (TIM)

@fabrizio moggio will provide feedback of the status in the next backlog call

• naming will be adapted based on updated scope, API ready for TSC approval.

• proposal: “IoT Network Optimization”

Feb 27, 2025: To be included in next TSC as all AP solved with IoT Network Optimization

128

China Unicom

Network Traffic Analysis

The API template is available in PR#129

INITIAL CONTEXT:

EasyCLA to be solved

LAST UPDATES:

Feb 13, 2025: consider applicability in https://github.com/camaraproject/ConnectivityInsights .

@Eric Murray Main difference could be session/device granularity in the monitoring, but could be handled with existing session Insight API. https://github.com/camaraproject/sessioninsights

AP: analyze current session/connectivity insight APIs to find posible gaps with network traffic proposal

Feb 27, 2025: similar to Network Health

Proposal:

• Include new sandbox for the API as different target (technically in terms of information (individual terminal or whole network, and parameters to be reported)than sessionInsight API.

• Leave the target of the API open to any Dedicated Network (private enterprise network, VPN, slice, public network…) not limiting the coverage of the API.

  • e.g. score of a 5G private network → score of a given network

  • AP China Unicom/All to confirm this proposal by monday 3rd of March.

    • Open whether 2 new sandbox repositories will be required for #127 #128

127

China Unicom

Network Health Assessment

The API template is available in PR#129

INITIAL CONTEXT:

EasyCLA to be solved

LAST UPDATES:

Feb 13, 2025: @Eric Murray could be considered as a new feature of the https://github.com/camaraproject/sessioninsights , more information is required from the Heath Score calculation. Use case are pretty similar, open whether the functionality is as well equal or requires an enhancement on current existing API. Gap analysis to be provided.

AP: provide more information on the health score calculation, and whether this functionality can already fits within the Session Insight API (use cases). Gap analysis to be provided to find any extension possible to complete existing APIs with new functionality.

Feb 27, 2025:

difference from SessionInsight:

• Target is private business networks, instead of public networks. (Aimed at enterprise network management capabilities, limited to private network)

• not targeted for individual terminal connection, but for whole private network (more computation load)

• the frequency of analysis requests will be periodic, whereas session insights can be called by any terminal, meaning frequent requests

Proposal:

• Include new sandbox for the API as different target (technically in terms of information (individual terminal or whole network, and parameters to be reported)than sessionInsight API.

• Leave the target of the API open to any Dedicated Network (private enterprise network, VPN, slice, public network…) not limiting the coverage of the API.

  • e.g. score of a 5G private network → score of a given network

  • AP China Unicom/All to confirm this proposal by monday 3rd of March.

20240523-01

API Backlog Governance

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

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

20240926-03

China Mobile

5G New Calling

• China mobile to further present the API proposal and include material in API  PR#31.

• https://github.com/camaraproject/WebRTC/issues/52 to discuss win WebRTC about relationship

20241010-02

ALL

IMEI Fraud

• Provide support from any company to take this API.

20250109-01

TIM

IoT Network Optimization

• AP Feb 13, 2025:Modify current API proposal (PR and name) with new use cases (TIM)

• AP Feb 27, 2025: To be included in next TSC as all AP solved with IoT Network Optimization

20250123-03

TEF/DT

Dynamic Predictive Connectivity Data

• AP Jan 23, 2025: Modify current API proposal according to comments.

• AP Feb 27, 2025: No overlap expected. API to be proposed to TSC.

20250213-02

China Unicom

SIM Historical Information

@Fan Yang Review issue offline and provide feedback and current status of the proposal.

20250213-04

China Unicom

Number Of Cards Under User's ID

For 115, 121, 122 information will b uploaded by @Fan Yang , issues to confirm with SIM Swap and KYC subprojects will be raised

20250213-05

China Unicom

Network Health Assessment

AP Feb 13, 2025: Provide more information on the health score calculation, and whether this functionality can already fits within the Session Insight API (use cases). Gap analysis to be provided to find any extension possible to complete existing APIs with new functionality.

AP Feb 27, 2025: Proposal:

1. Introduce a new sandbox for the API, considering its distinct scope in terms of target (individual terminal vs. whole network) and reported parameters.

2. Keep the API target open to any Dedicated Network (e.g., private enterprise network, VPN, network slice, public network) to ensure broader coverage.

3. Example: Scoring a 5G private network → Evaluating the performance of a given network.

4. AP China Unicom and all relevant stakeholders to confirm the proposal by Monday, March 3rd.

20250213-06

China Unicom

Network Traffic Analysis

AP Feb 13, 2025: Analyze current session/connectivity insight APIs to find posible gaps with network traffic proposal

 AP Feb 27, 2025: Proposal:

• Include new sandbox for the API as different target (technically in terms of information (individual terminal or whole network, and parameters to be reported)than sessionInsight API.

• Leave the target of the API open to any Dedicated Network (private enterprise network, VPN, slice, public network…) not limiting the coverage of the API.

  • e.g. score of a 5G private network → score of a given network

  • AP China Unicom/All to confirm this proposal by monday 3rd of March.

  • Open whether 2 new sandbox repositories will be required for #127 #128 for TSC validation.

20250213-07

China Unicom

eSIM Remote Management

AP Feb 27, 2025:

• China unicom to upload additional information and flows of the API proposal.

• Update: include more information on interfaces to included in the proposal (e.g. IF6)

closed

20250227-01

China Unicom

Voice Notification & Voice Verification Code

• AP Feb 13, 2025: China Unicom to review possible match with 5G New Calling API proposal PR#31.

• AP Feb 27, 2025: comment raised about the similarity or match with 5G new calling API proposal as targeted for applications to take advantage of the IMS network and callers. To check PR#31. For 157 &160 reach offline with china mobile to understand matching between APIs.

20250313-01

China Unicom

eSIM Remote Management

AP Mar 13, 2025:

• China unicom to create a PR to ensure API proposal template is not using telco language.

DP #

DP description

Status