DRAFT MINUTES
Attendees
| Organization | Name |
| Orange | |
| Charter Communications | Christopher Aubut ; Justin Pace |
| Telefonica | |
| Vodafone | |
| Ericsson | |
| AT&T | |
| DT | @Noel Wirzius |
| T-Mobile US | |
| KDDI | |
| Slagen | |
| Nokia | |
| China Telecom | |
| ZTE | |
| KPN | |
| GSMA | |
| Centilion |
...
New Procedures in API Backlog WG meetings
A number of improvements are under discussion with leadership team of OGW project (Henry), CAMARA Project (Markus), Product Definition WS (Helene) and TSC (Herbert). As of today, the WG adopted agreements are three:
- To close the agenda SEVEN DAYS BEFORE the conf. call.
- In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.
- Exceptional situations will be treated separately.
- New schedule of conf. calls **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)
- 2nd Thursday of the month (10-11 CET)
- 4th Thursday of the month (15-16 CET)
- Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them.
Meeting Minutes within Wiki instead of Github
...
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 20th June:
...
Noel and eric will be joinning Desvice status meeting
Backlog table
- Table updated in PR#51 (merged)
Review of Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240523-01 | API Backlog Governance | Ricardo to reach up TelecomXchange and Netfocusin Technologies to see if the could connect next meetings | 23 24 18 | 23/05/2024 | Open |
| 20240523-02 | API Backlog Governance/China Unicom | Open an issue within DeviceStatus subproject to check overlaps regarding Shutdown Service Status | 34 | 23/05/2024 | Closed |
| 20240523-03 | KDDI | Toshi validate with KYC participants if Telco Scoring API may fit within KYC familiy | 41 | 23/05/2024 | Closed |
| 20240523-07 | DT | Best interconnection: Review wether there is overlap with EdgeCloud subproject | 20 | 23/05/2024 | Open |
| 20240613-01 | API Backlog Governance | Ricardo to merge the templates (Device Data Volume and Device Quality indicator | 19 28 | 13/06/2024 | Closed |
| 20240613-02 | KDDI | Show the differences/similarities between Number recycling and shutdown service/Tenure in the next meeting (prepare a slide or two) | 54 | 13/06/2024 | Closed |
Discussion
Current Issues
| 17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. | 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. |
| 4 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | 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. |
| 18 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 |
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 |
| 19 | Deutsche Telekom | New Proposal: Device Quality Indicator | 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) |
| 23 | TelecomsXChange | New Proposal: Carrier Wholesale Pricing 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 |
| 24 | Netfocusin Technologies | New Proposal: Steering of Roaming Management | 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 |
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) | |
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 | |
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 | |
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. | |
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 | |
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 | |
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. | |
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 | |
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 | |
Ericsson | New API proposal-Dedicated Networks The API template is available #59 | Thorsten presented the proposal: Material here
There have been a similar work in a TMF API. Pierre offere himself to Thorsten to reach up |
...
| 20 | Deutsche Telekom | Best Interconnection | Seek for support ACTION: See if there is any overlap within EdgeCloud |
| 22 | T-Mobile US | Capability and Runtime Restrictions | 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 |
...
Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240523-01 | API Backlog Governance | Ricardo to reach up TelecomXchange, Totogi and Netfocusin Technologies to see if the could connect next meetings | 23 24 18 | 23/05/2024 | Open |
| 20240523-07 | DT | Best interconnection: Review wether there is overlap with EdgeCloud subproject | 20 | 23/05/2024 | Open |
| 20240627-01 | China Unicom, KDDI, Vodafone, DT | Check whether Tenure + Shutdown service + Number recycling fit in KYC (parts involved align internally) | 54 2 34 | 28/06/2024 | Open |
| 20240627-02 | API Backlog Governance | New use cases are usually proposed. Modify the Scope template to show this and approve | 53 | 28/06/2024 | Open |
Decision Points
| DP # | DP description | Related issue |
| 20240627-01 | 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) | |
| 20240627-02 | Receive SMS is approved to be created as part of the scope of the ShortMessageService group. Scope of the group to be modified (same repo and family will apply) | |
| 20240613-01 | New repo name is approved (Region User Count → Region Device Count) | 48 |
| 20240613-02 | Scope Enhancement: KYC-Match API - Scoring logic is approved | 45 |
AoB
Next Backlog conf. call: 11th July, 10-11 UTC+2.
Next TSC conf. call: 4th July, 10-11,30 UTC+2
Q&A
How does CAMARA API pipeline work?
...