DRAFT MINUTES
Attendees
...
Ricardo Serrano Gutierrez @agustinmartin Jorge Garcia Hospital
...
...
Agenda Proposal
...
OGW Drop #3 APIs: #19 (Device Quality Indicator)
Other APIs: #17 (Consent and Measurement), #18 (Receive SMS), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #29 (Call Status), #28 (Device Data Volume)
Governance: #4 (Structures and roles, RACI, Maintainers initiative)
...
#20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #2 (Tenure), #27 (Verified Caller)
...
Antitrust Policy
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LinusFoundation.
...
...
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
- CAMARA community agreed that meeting minutes would only be recorded in the wiki
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 18th May:
- The subgroups/repos have been created:
- Tenure: Maintainers and Codeowners need to be provided, scope is pending
- VerifiedCaller: Maintainers and Codeowners have already been provided, scope is pending
- In the sake of the health of the CAMARA group, so that the projects do not lose their activity as soon as they are born, it will be proposed that in order to approve new API proposals, these must be supported by at least 3 companies (MNO or suppliers indistinctly). An issue will be opened within governance encompassing this. TSC will take a decission next meeting
- This issue seems to be under discussion, some companies have commited to make a more relaxed alternative such a sandbox
Other topics
- New API Backlog GitHub Repo have been created here. Issues have been migrated, PRs will be migrated once they are approved. New PRs and Issues need to be opened in the new repo.
Codeowners:
Anyone else commits to be codeowner?
Next steps:
- Keep PRs in the old repo and the new PRs will directly need to be opened in the new repo
- Issues will be moved to the new repo
Backlog table
- Table updated in PR#51 (merged)
Review of Action Points
...
AP Owner
...
AP description
...
Related issue
...
Due date
...
Status
...
WG delegates
...
Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them.
...
...
2024/02/21
...
Open
...
Centilion
...
To draft a simple figure illustrating the API logic with a high-level workflow, and attach it to the PR.
...
...
2024/02/21
Open
...
Governance
...
Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC
...
2024/03/14
...
Open
...
...
...
...
Discussion
Current Issues
...
Finishing documentation, Waiting for Real Time Bidding (RTB) standard to come up with the last versions so to provide further details
...
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
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
...
DRAFT MINUTES
Attendees
| Organization | Name |
| Orange | |
| Charter Communications | Christopher Aubut |
| Telefonica | Ricardo Serrano Gutierrez @agustinmartin Jorge Garcia Hospital |
| Vodafone | Eric Murray |
| Ericsson | Jan Friman |
| AT&T | Pierre Close |
| DT | Noel Wirzus |
| T-Mobile US | |
| KDDI | Yasu Wakama |
| Slagen | |
| Nokia | |
| China Telecom | |
| ZTE | |
| KPN | |
| GSMA | Helene Vigue |
| Centilion | Nick Venezia |
Agenda Proposal
- Antitrust Policy
- Approval of minutes of last conf. call
- Recent Updates & Recap
- Review of Action Points
- Discussion
OGW Drop #3 APIs: #19 (Device Quality Indicator)
Other APIs: #17 (Consent and Measurement), #18 (Receive SMS), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #29 (Call Status), #28 (Device Data Volume)
Governance: #4 (Structures and roles, RACI, Maintainers initiative)
- Clossing Issues
#20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #2 (Tenure), #27 (Verified Caller)
- Action Points
- AOB
- Q&A
Antitrust Policy
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LinusFoundation. |
 |
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
- CAMARA community agreed that meeting minutes would only be recorded in the wiki
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 18th May:
- The subgroups/repos have been created:
- Tenure: Maintainers and Codeowners need to be provided, scope is pending
- VerifiedCaller: Maintainers and Codeowners have already been provided, scope is pending
- In the sake of the health of the CAMARA group, so that the projects do not lose their activity as soon as they are born, it will be proposed that in order to approve new API proposals, these must be supported by at least 3 companies (MNO or suppliers indistinctly). An issue will be opened within governance encompassing this. TSC will take a decission next meeting
- This issue seems to be under discussion, some companies have commited to make a more relaxed alternative such a sandbox
Other topics
- New API Backlog GitHub Repo have been created here. Issues have been migrated, PRs will be migrated once they are approved. New PRs and Issues need to be opened in the new repo.
Codeowners:
Anyone else commits to be codeowner?
Next steps:
- Keep PRs in the old repo and the new PRs will directly need to be opened in the new repo
- Issues will be moved to the new repo
Backlog table
- Table updated in PR#51 (merged)
Review of Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20230208-02 | WG delegates | Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them. | 2024/02/21 | Open | |
| 20230208-01 | Centilion | To draft a simple figure illustrating the API logic with a high-level workflow, and attach it to the PR. | 2024/02/21 | Open | |
| 20240314-01 | Governance | Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC | 367 | 2024/03/14 | Open |
| 20240411-01 | Deustche Telekom | Noel updating proposal with new fields. Start in parallel while device status API is split | 375 |
| Open |
| 20240411-03 | Telefonica&DT | Modify the README for the QualityOnDemand subproject and include the new Scope enhancement | 402 404 |
| Closed |
| 20240425-02 | Centillinon | Next API Backlog meeting, Nick to bring new use cases and endpoints | 351 |
| Open |
Discussion
Current Issues
Closed Issues
...
Owner
...
Repository
...
...
China Telecom
Verified Caller
...
...
Vodafone
...
Tenure
...
New Issues
...
Action Points
AP Owner
AP description
Related issue
Due date
Status
| 17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. | Finishing documentation, Waiting for Real Time Bidding (RTB) standard to come up with the last versions so to provide further details 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 The issue is not eligible to be closed yet. | |||||
| 18 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 |
This issue was not treated in this conference call The issue is not eligible to be closed yet. DECISION: not treated to be treated in following session | |||||
| 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 Isue 375 and 412 would be integrating within the Device Status subproject The subgroup people is okay with this The issue is not eligible to be closed yet. to be treated in following session DECISION: 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 Quality Indicator | |||||
| 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. DECISION: not treated to be treated in following session | 19 | Deutsche Telekom ACTION: Ricardo to reach up TelecomXchange to see if the could connect next meetings | |||
| 24 | Netfocusin Technologies | New Proposal: Device Quality IndicatorSteering of Roaming Management 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 Isue 375 and 412 would be integrating within the Device Status subproject The subgroup people is okay with thisPR#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. DECISION: not treatedto be treated in following session 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 | DECISION: Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue) Both issue 19 and 28 to to the DeviceStatus family and separate repositories (deviceStatus) → Device Quality Indicator | 23 | TelecomsXChange | New Proposal: Carrier Wholesale Pricing First YAML avaliable here | 24 | Netfocusin Technologies | |
Deutsche Telekom | New API Proposal: Device Data Volume New template in PR#39 | DECISION: 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 | ||||||
Rogers | New API Proposal: Call Status | Issue is closed due to lack of activity → redacted | China Unicom | New API Proposal: Shutdown ServiceStatus The API tempate is available in PR#32 | China Mobile | 5G New Calling The API template is available PR#31 | ||
Telefonica | New API Proposal: Telco Scoring The API template is available #42 Input from OGW Drop 4 | Presented slides: API-Overview-TelcoScore.pptx Scoring is a simple algortithm/model but need to be aligned within all the operators Splicit consent is needed. How the model is going to be discussed?
Unified model for all the countries may lead into dificulties in order to fit the API within CAMARA Scope ACTION: Toshi validate if This APImay fit within KYC API familiy ACTION: Jorge Reach out to Nick by email | ||||||
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 participants | China Unicom | Scope Enhancement: Name change RegionUserCount The API template is available #47 |
Closing Issues
...
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
repositories (deviceStatus) → Device Data Volume | |||
Rogers | New API Proposal: Call Status | Issue is closed due to lack of activity → redacted | |
China Unicom | New API Proposal: Shutdown ServiceStatus The API tempate is available in PR#32 | Not treated (relations with device status to be considered) To be treated in next session ACTION: Open an issue within DeviceStatus subproject to check overlaps. | |
China Mobile | 5G New Calling The API template is available PR#31 | Not treated 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 Scoring is a simple algortithm/model but need to be aligned within all the operators Splicit consent is needed. How the model is going to be discussed?
Unified model for all the countries may lead into dificulties in order to fit the API within CAMARA Scope ACTION: Toshi validate if This APImay fit within KYC API familiy ACTION: Jorge Reach out to Nick by email | |
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 | |
China Unicom | Scope Enhancement: Name change RegionUserCount The API template is available #47 |
Closing Issues
| 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 |
Closed Issues
| Issue | Owner | API | Repository |
China Telecom | Verified Caller | VerifiedCaller | |
Vodafone | Tenure | Tenure |
New Issues
| 37 | Vodafone | Move Simple Edge Discovery to own repository | Closed, moved to new separate repo. |
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-02 | API Backlog Governance/China Unicom | Open an issue within DeviceStatus subproject to check overlaps regarding Shutdown Service Status | 34 | 23/05/2024 | Open |
| 20240523-03 | KDDI | Toshi validate with KYC participants if Telco Scoring API may fit within KYC familiy | 41 | 23/05/2024 | Open |
| 20240523-04 | Telefonica | Jorge Reach out to Nick by email | 41 | 23/05/2024 | Open |
| 20240523-05 | KDDI | Toshi validate with KYC participants if TScoring Logic Scope Enhancement may fit within KYC familiy | 45 | 23/05/2024 | Open |
| 20240523-06 | API Backlog Governance | Create a API Scope Enhancement Template | TBO | 23/05/2024 | Open |
| 20240523-07 | DT | Best interconnection: Review wether there is overlap within EdgeCloud subproject | 20 | 23/05/2024 | Open |
Decision Points
| DP # | DP description | Related issue |
| 20240523-01 |
Verified Caller API move for approval, to be treated in following TSC
Tenure API move for approval, to be treated in following TSC
Move to TSC if there is enough support for this API (Interested parties provide comments in the Issue) Both issue 19 and 28 to the DeviceStatus family and separate repositories → Device Quality Indicator | ||
| 20240523-02 | Move to TSC if there is enough support for this API (Interested parties provide comments in the Issue) Both issue 19 and 28 to the DeviceStatus family and separate repositories → Device Data Volume |
AoB
Next Backlog conf. call: 23th May, 15-16 UTC+2.
Next TSC conf. call: 16th May, 16-1706th June, 10-11,30 UTC+2
Q&A
How does CAMARA API pipeline work?
...