Page History

Published new standards, Next meeting (this time) Nick will bring all the documentationa present everything putted together

The issue is not eligible to be closed yet.

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.

Ricardo is currently working on modeling a new table

Strugling with the new Table model.

Bring the PRs from the old repo 

Makes sense to bring the table to confluence? 

GitHub seems to be more accesible and is visited by further people (devs. etc.)

The issue is not eligible to be closed yet.

• 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 formaly proceed with the scope enhancement os the SMS group

Deutsche Telekom

New Proposal: Device Quality Indicator
The API template is available in PR#380
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 commited 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)

TelecomsXChange

New Proposal: Carrier Wholesale Pricing
The API template is available in PR#393

First YAML avaliable here

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

ACTION: Ricardo to reach up TelecomXchange to see if the could connect next meetings

Netfocusin Technologies

New Proposal: Steering of Roaming Management
The API template is available in PR#398

Does not seem to be in the Scope of Camara. 

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

ACTION: Ricardo to reach up Netfocusin Technologies to see if the could connect next meetings

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)

34

China Unicom

New API Proposal: Shutdown ServiceStatus

The API tempate is available in PR#32

(relations with device status to be considered)

Device Status seems to not fit withion the API proposal, anyhow Yang will be opening an issue to check this

May fit better in other API Status based group (Number verification maybe)

Wait until is discussed in device status group (Next wednesday 19th at 11h CEST → LINK)

ACTION: Open an issue within DeviceStatus subproject to check overlaps. → There should be different APIs (device Status and shutdown services)

Number verification doesn t fit either as it is more based in subscription (name change?)

Overlap with Tenure and number recycling

ACTION: Owner to check Overlap with Tenure and number recycling

35

China Mobile

5G New Calling

The API template is available PR#31

Not treated

Telefonica and Vodafone willing to see the presentation to check whether there is support for this

To be treated in next session

41

Telefonica

New API Proposal: Telco Scoring

The API template is available #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 APImay fit within KYC API familiy → The issue was rised 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.

45

Telefonica

Scope Enhancement: KYC-Match API -Scoring logic 

The API template is available #46

This is just an enhancement of the current API. 

Looks fine as an Enhancement. SHould work without scoring due to limitation in some countries (not all responses include scoring, some cases does not make sense). 

Optional parameter in the output

ACTION: Toshi validate if This API may fit within KYC API subproject

ACTION: Scope Enhancement Template should be created → DONE can continue with the discussion

Once the Scope Enhancement is approved the README of the KYC sg need to be updated

DECISION ALready developed approved in the backlog

48

China Unicom

Scope Enhancement: Name change RegionUserCount

The API template is available #47

There is agreement in the name change so 

DECISION: New repo name is approved

50

Verizon

Device Management

The API template is available #30

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

53

API Backlog

Scope Enhancement Template

The API template is available #52

New use cases are usually proposed. Modify the template to show this and approve

54

KDDI

Number Recycling

The API template is available 55

Difference with shutdown service? 

Check the differences.

Shutdown service is not linked to a contract

Probable comon scopes with shutdown service + Number reciclyng + Tenure

For Tenure two APIs have been proposed and differ from this ones (tenure is more refered the client itself rather than devices or mSISDNS)

ACTION: Show the differences/similarities in the next meeting (prepare a slide or two)

Check whether Tenure + Shutdown service + Number recycling fit in KYC (parts involved align internally)

Proposal is to include the API in the same API but separate repos

Move to TSC after discussion of the rest of APIS 

60

Ericsson

New API proposal-Dedicated Networks

The API template is available #59

Deutsche Telekom

Best Interconnection
The API template is available in PR#381
Input from OGW Drop 3

Seek for support

ACTION: See if there is any overlap within EdgeCloud

T-Mobile US

Capability and Runtime Restrictions
The API template is available in PR#384

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

intitial YAML files to be included in the API TEMPLATE

The issue was not treated in this conference call

Owner

Repository

27 

China Telecom

 Verified Caller 

2

Vodafone

 Tenure

New API Proposal - IMEI Fraud Check API

The template is available in PR#64

AP Owner

AP description

Related issue

Due date

Status

DP description

Related issue

Formal agreement from the Device Status subgroup is required for Device Data Volume and Device Quality indicator. To be treated in next meeting (Device Status)

19 28

New repo name is approved (Region User Count →  Region Device Count)

Scope Enhancement: KYC-Match API - Scoring logic is approved