...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees
...
Attendees
Organization | Name |
Orange | Ludovic Robert |
Charter Communications | |
Telefonica | |
Vodafone | |
Ericsson | |
AT&T | Pierre Close |
DT | |
T-Mobile USKDD | |
KDDI | |
Slagen | |
Nokia | Tanja de Groot |
China Telecom | |
ZTE | |
KPNGSMA | Huub Appelboom |
GSMA | Helene Vigue |
Centilion |
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)
OGW Drop #4 APIs: #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling)
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)
Scope Enhancement: #45 (KYC-Match API - Scoring Logic), #48 (RegionUserCount)
Governance: #4 (Structures and roles, RACI, Maintainers initiative), #53 (Scope Enhancement API Template)
- Clossing Issues
- 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
GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress.
The 3 APIs are
- IMEI Fraud
- Best Interconnect
- Device Quality Indicator
For clarity if any API is not a priority for OGW anymore at this point in time, we still expect they can progress independently in CAMARA.
@Helene Vigue:
...
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
...
(Consent and Measurement), #18 (Receive SMS), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #29 (Call Status), #28 (Device Data Volume)
Scope Enhancement: #45 (KYC-Match API - Scoring Logic), #48 (RegionUserCount)
Governance: #4 (Structures and roles, RACI, Maintainers initiative), #53 (Scope Enhancement API Template)
- Clossing Issues
- 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 6th June:
- The subgroups/repos have been created:
- Tenure: Maintainers and Codeowners need to be provided, scope is pending → KDDI can not commit to be Maintainer nor Codeowner. Codeowners vodafone, Orange and DT
- 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 2 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
- To launch the Repo itis needed 2 people from differen companies
- Get formal commitment for TSC → Ricardo
Other topics
GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress.
The 3 APIs are
- IMEI Fraud
- Best Interconnect
- Device Quality Indicator
For clarity if any API is not a priority for OGW anymore at this point in time, we still expect they can progress independently in CAMARA.
@Helene Vigue:
The progress from camara side wont stop, but GSMA wont tak them as a priority
Vodafone commited to support Device Quality indicator (and device data volume)
Any extra supporters?
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 |
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 | Close |
20240523-04 | Telefonica | Jorge Reach out to Nick by email | 41 | 23/05/2024 | Close |
20240523-05 | KDDI | Toshi validate with KYC participants if TScoring Logic Scope Enhancement may fit within KYC familiy | 45 | 23/05/2024 | Close |
20240523-06 | API Backlog Governance | Create a API Scope Enhancement Template | 53 | 23/05/2024 | Close |
20240523-07 | DT | Best interconnection: Review wether there is overlap within EdgeCloud subproject | 20 | 23/05/2024 | Open |
Discussion
Current Issues
17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. | Not treated 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 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. 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 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. | ||||||||
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 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, 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 | ||||||||
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 this The issue is not eligible to be closed yet. to be treated in following sessionPR#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 treated 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 | 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 subproject ACTION: Scope Enhancement Template should be created | |||||||||
China Unicom | Scope Enhancement: Name change RegionUserCount The API template is available #47 | Verizon | Device Management The API template is available #30 | KDDI | Number Recycling The API template is available 55 | API Backlog | Scope Enhancement Template The API template is available #52separate repositories (deviceStatus) → Device Data Volume ACTION Ricardo to merge the templates | ||||
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. → To Do | |||||||||
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 raised but still under discussion 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 → 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. | |||||||||
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) | |||||||||
API Backlog | Scope Enhancement Template The API template is available #52 | New use cases are usually proposed. Modify the template to show this |
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 |
...
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-0407 | 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 | 45DT | Best interconnection: Review wether there is overlap with EdgeCloud subproject | 20 | 23/05/2024 | Open |
2024052320240613-0601 | API Backlog Governance | Create a API Scope Enhancement Template | TBO | 23/05Ricardo to merge the templates (Device Data Volume and Device Quality indicator | 19 28 | 13/06/2024 | Open | ||||||
2024052320240613-0702 | DT | Best interconnection: Review wether there is overlap within EdgeCloud subproject | 20 | 23/05KDDI | Show the differences/similarities between Number recycling and shutdown service/Tenure in the next meeting (prepare a slide or two) | 54 | 13/06/2024 | Open |
Decision Points
DP # | DP description | Related issue | |||
20240523-01 | Move to TSC if , check wether there is enough support for this API (Interested parties provide comments in the Issuethe Issue, Vodafone commited and a third supporter is being queried) Both issue issue 19 and 28 to to the DeviceStatus family and separate repositories → Device Quality Indicator | ||||
20240523-02 | Move to TSC if , check wether there is enough support for this API (Interested parties provide comments in the Issue, Vodafone commited and a third supporter is being queried) Both issue issue 19 and 28 to the DeviceStatus family and separate repositories repositories → Device Data Volume | 20240523-03 | Call Status API proposal overlaped with existing CAMARA projects and owner REDACTED Issue. Issue is closed | ||
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: 27th June, 16-17 UTC+2.
Next TSC conf. call: 20th June, 16-17,30 UTC+2
Q&A
How does CAMARA API pipeline work?
...