Page Comparison

Organization

Name

Orange

Ludovic Robert

Charter Communications

 Christopher Aubut

CableLabs

TelefonicaJorge Garcia Hospital

Vodafone

Kevin Smith Eric Murray Kevin Smith

EricssonThorsten Lohmar

Jan Friman

AT&T

Pierre Close

T-Mobile US

G. Murat Karabulut

KDDIYusuke Nakano

Slagen

Nokia 

China Telecom 

ZTE

KPN

Huub Appelboom

GSMA

Reg Cox Mark Cornall

Centilion 

Chunghwa Telecom 

Deutsche Telekom

MTN 

China Mobile

Haojie Li Keguang He zhangruqian

Verizon

Mahesh Chapalamadugu

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

MEETING UPDATEAction: Clarifying with interested parties whether this may be a possible API or a Framework etc.

MEETING UPDATE:

Not treated

4

Governance

Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments)

The aim is to update the governing document to reflect on the updated changes on API submission pipeline, according to the new structure of the API backlog table.

PR is uploaded: New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog (github.com)

PR to be checked and confirmed before issue can be closed

MEETING UPDATEAction: Partners to review and validate

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

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 treated

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)

Pending to clarify scope with VerifedCaller

MEETING UPDATE:

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.

50

Verizon

Device Management

The API template is MEETING UPDATE:

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

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

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.

61 

66

Vodafone

Scope Enhancement for Network infoMEETING UPDATE:

Mahesh Chapalamadugu AP to upload documentation

63

MTN

New API proposal - IMEI Fraud

The API template is available PR#72

To clarify if new API is proposed  in the Device Status Family or it's an enhancement over an existing API.

To clarify its relationship with Open Gateway Telco Finder API → 

Kevin opened PR#72 to complement Issue PR#66. Both still open.

Noel commented that this is likely to be accepted

New repository is likely to be required

Comments have been provided in the issue

• Device Status group to confirm, TSC will review the match or alignment with Telco finder (GSMA)

MEETING UPDATE: 

 Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143

Enhancement proposal to be updated by Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision.

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.

MEETING UPDATE:

Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. Waiting for MTN for moving on with this API. Maybe to be included in the Device Identifier family.

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)

MEETING UPDATE:

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)

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

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

83

China Mobile

Model As A Service Familyavailable 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.

MEETING UPDATE:

 @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

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

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:

Haojie Li proposes to move to next TSC for approval → Agreed

85

China Mobile

Knowledge Base - Manage

The API template is available in PR#84 - Knowledge Base - Manage

As per 83

86

China Mobile

Q&A Assistant - Manage

The API template is available in PR#84 - Q&A Assistant - Manage

As per 83

87

China Mobile

Q&A Assistant - Service

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

China Mobile presented the API

MEETING UPDATE:

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.

85

China Mobile

Knowledge Base - ManageQ&A Assistant - Service

As per 83

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

METING UPDATE:

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

Kevin Smith

91

Telefonica

Fixed Lines in Location

The API template is available in PR#84 - Knowledge Base - Manage

MEETING PR#92

METING UPDATE:

86

China Mobile

Q&A Assistant - Manageto be open in location group

93

Telefonica

Line Eligibility for Carrier Billing API

The API template is available in PR#84 - Q&A Assistant - Manage

MEETING PR#94

METING UPDATE:

87

China Mobile

MEETING UPDATE:

89

China Mobile

IP High-throughput Elastic Network not treated

Issue #

Company

Summary

Status Update

22

T-Mobile US

Capability and Runtime Restrictions

The API template is available in 

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

MEETING UPDATE:

• 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

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

1934

Deutsche TelekomChina Unicom

New API Proposal: Device Quality IndicatorShutdown ServiceStatus (SubscriptionStatus)

The API template is available in PR#57

Input from OGW Drop 3

Noel proposed Device Status subgroup to integrate their APIs within Noel's. Noel to make the proposal to the API Backlog and provide update

Two proposals Issue 19 and 28 would be integrating within the Device Status subproject The subgroup people is okay with this

The issue is not eligible to be closed yet.

Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue, Vodafone committed and a third supporter is being queried) Both issue 19  and 28 to the DeviceStatus family and separate repositories (deviceStatus) →  Device Quality Indicator

DECISION formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status)

DECISION There is agreement Orange, DT and VDF, next backlog meeting there should be the outcome for this issue

Pending to confirm codeowner/maintainers for repo creation, email sent

• All actions complete

• Issue #19 to be closed. PR #57 already merged.

• Old Working Groups PR #414 to closed

MEETING UPDATE:

• Group to start activity, item to be deleted from closing issue table

28

Deutsche Telekom

New API Proposal: Device Data Volume

New template in PR#39

Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue) Both issue 19  and 28 to the DeviceStatus family and separate repositories (deviceStatus) → Device Data Volume

DECISION formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status)

DECISION There is agreement Vonage, DT and VDF, next backlog meeting there should be the outcome for this issue

Pending to confirm codeowner/maintainers for repo creation, email sent

• All actions complete

• Issue #28 to be closed. PR #39 already merged.

MEETING UPDATE:

• Group to start activity, item to be deleted from closing issue table

34

China Unicom

New API Proposal: Shutdown ServiceStatus (SubscriptionStatus)

The API template is available in PR#32

DECISION  Separate Repos should be created but same family (KYC) in order to have coordination meeting

Pending to confirm codeowner/maintainers for repo creation, email sent

Included in today's TSC approval.

• Issue #34 can be closed and PR #32 merged

MEETING UPDATE:

• Additional codeOwner required

54

KDDI

Number Recycling

The API template is available 55

NumberRecycling

Pending Codeowners and maintainers (requested in comment)

MEETING UPDATE:

• First initial list included, pending only participants from DT

70

Cablelabs

New API proposal - Quality by Design

The API template is available #71

Slides available here: here
YAML available here: here

Proposal is that QbD be a scope enhancement to Connectivity Insights

Will likely require new API, hence new repository required

QdD supporters will attend Connectivity Insights meeting next week to finalise proposal

Awaiting outcome of Connectivity Insights meeting before finalising if new repository required

• New repo to be created (new separated API) but included into the existing Connectivity insights family. To be confirmed base on the last meeting minutes. As soon as clarified, it will be included in next TSC

DECISION :

1.  Herbert Damker creates the repo QualityByDesign 

2.  Ben Hepworth provides user story/ies, → AP

3. (Project team) Discuss the concept & propose rename → AP

4.  (TSC) Adjust the name

MEETING UPDATE:

• Repo created

• Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion

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

MEETING UPDATE:

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.  

MEETING UPDATE:

• API approved, repo will be created after final name is proposed by the group (email sent)

• Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion

60

Ericsson

New API proposal-Dedicated Networks

The API template is available PR#59

Thorsten presented the proposal: Material here

Image Removed

There have been a similar work in a TMF API. Pierre offered himself to Thorsten to reach up

DECISION New repo/subproject to be created and a family that groups both NSB and DN

ACTION Telefonica providing comments this afternoon and moving to TSC → Action complete

Comments from TEF addressed in Issue PR#60

ACTION: Eric to check with Miranda in Issue PR#60 if her preference is for separate sub-projects, or for DN to join NSB sub-project

No response regarding this, pending to response

MEETING UPDATE:

Discussion regarding separate or not separate repos.

Telefonica supports having separate repos but having the conversation in the same forum as part of a unified family

DECISION: Move to tsc taking care of this comment and expecting the administrative work to be clarified there. Someone for NSB group (Huawei, China etc.) should be connecting tsc that day at least to be aware of this

ACTION: Thorsten to reach up NSB group by it mailing list proposing to join the TSC meeting. Next TSC meetings: 

19/09/24 at 16:00 CEST / 14:00 UTC / 07:00 PST

Meeting Registration / Join

03/10/24 at 10:00 CEST / 08:00 UTC / 01:00 PST

Meeting Registration / Join

MEETING UPDATE:

PR#32

DECISION  Separate Repos should be created but same family (KYC) in order to have coordination meeting

Pending to confirm codeowner/maintainers for repo creation, email sent

Included in today's TSC approval.

• Issue #34 can be closed and PR #32 merged

ACTION Pending to validate remaining codeOwner

MEETING UPDATE:

54

KDDI

Number Recycling

The API template is available 55

NumberRecycling

Pending Codeowners and maintainers (requested in comment)

MEETING UPDATE:

Group created and participants included, issue to be deleted. → PR merged

70

Cablelabs

New API proposal - Quality by Design

The API template is available #71

Slides available here: here
YAML available here: here

Proposal is that QbD be a scope enhancement to Connectivity Insights

Will likely require new API, hence new repository required

QdD supporters will attend Connectivity Insights meeting next week to finalise proposal

Awaiting outcome of Connectivity Insights meeting before finalising if new repository required

• New repo to be created (new separated API) but included into the existing Connectivity insights family. To be confirmed base on the last meeting minutes. As soon as clarified, it will be included in next TSC

DECISION :

1.  Herbert Damker creates the repo QualityByDesign 

2.  Ben Hepworth provides user story/ies, → AP

3. (Project team) Discuss the concept & propose rename → AP

4.  (TSC) Adjust the name

MEETING UPDATE:

Group created and participants included, issue to be deleted. → PR to be merged

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:

• API approved, repo will be created after final name is proposed by the group (email sent)

• Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion

MEETING UPDATE:

Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion

60

Ericsson

New API proposal-Dedicated Networks

The API template is available PR#59

Thorsten presented the proposal: Material here

Image Added

There have been a similar work in a TMF API. Pierre offered himself to Thorsten to reach up

DECISION New repo/subproject to be created and a family that groups both NSB and DN

ACTION Telefonica providing comments this afternoon and moving to TSC → Action complete

Comments from TEF addressed in Issue PR#60

ACTION: Eric to check with Miranda in Issue PR#60 if her preference is for separate sub-projects, or for DN to join NSB sub-project

No response regarding this, pending to response

MEETING UPDATE:

Discussion regarding separate or not separate repos.

Telefonica supports having separate repos but having the conversation in the same forum as part of a unified family

DECISION: Move to tsc taking care of this comment and expecting the administrative work to be clarified there. Someone for NSB group (Huawei, China etc.) should be connecting tsc that day at least to be aware of this

ACTION: Thorsten to reach up NSB group by it mailing list proposing to join the TSC meeting. Next TSC meetings: 

19/09/24 at 16:00 CEST / 14:00 UTC / 07:00 PST

Meeting Registration / Join

03/10/24 at 10:00 CEST / 08:00 UTC / 01:00 PST

Meeting Registration / Join

Pending: Codeowners and Maintainers to be included

MEETING UPDATE:

Group created and participants included, issue to be deleted. → PR to be merged

61 

66

Vodafone

Scope Enhancement for Network info

The API template is available PR#72

To clarify if new API is proposed  in the Device Status Family or it's an enhancement over an existing API.

To clarify its relationship with Open Gateway Telco Finder API → 

Kevin opened PR#72 to complement Issue PR#66. Both still open.

Noel commented that this is likely to be accepted

New repository is likely to be required

Comments have been provided in the issue

• Device Status group to confirm, TSC will review the match or alignment with Telco finder (GSMA)

 Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143

Pending: Enhancement proposal to be updated by Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision.

MEETING UPDATE:

As all solved, issue to be deleted → PR to be merged

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: