...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees
...
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: #27 (Verified Caller), #35 (5G New Calling), #34 (Shutdown Service Status), #2 (Tenure)
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
- 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 April:
- The API Backlog subgroup will have its own github repo. Initial Maintainers have been requested. Those of you that have been active within the last meetings have received an email requesting for comitment/refusal:
...
- The subgroups have been created: Network Access Management, Most Frequent Location + Device Visit Location (Location Insights)
- 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 e under discussion, some companies have commited to make a mor 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 there are approved. New PRs and Issues need to be opened in the new repo.
Codeowners:
Anyone else commits to be codeowner?
ACTION: Ricardo Serrano Gutierrez to include Chris as a Codeowner
- Keep the pull request in the old repo and the new entering ones move them to the new repo
- Issues will be moved to the new repo
Backlog table
- Table updated in PR#406
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
...
- AP 20230208-01 still open.
The issue is not eligible to be closed yet.
Nick will be working within next weeks on providing what camara can work on within this API
ACTION: Next API Backlog, Nick will bring new use cases and endpoints
...
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
New WoW 3 companies needed
Nick propose to focus more in the Commercial viability of the proposal in orther to rise up interest of other companies
Huub points out the sensibility of posting commercial strategies within this type of forums as many companies are potential competitors
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
This issue was not treated in this conference call
The issue is not eligible to be closed yet.
DECISION: not treated
...
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 Isue 375 and 412 would be integrating within the Device Status subproject
The issue is not eligible to be closed yet.
...
TelecomsXChange
...
New Proposal: Carrier Wholesale Pricing
The API template is available in PR#393
First YAML avaliable here
...
DRAFT MINUTES
Attendees
| Organization | Name |
| Orange | |
| Charter Communications | |
| Telefonica | |
| Vodafone | |
| Ericsson | |
| AT&T | |
| DT | |
| T-Mobile US | |
| KDDI | |
| Slagen | |
| Nokia | |
| China Telecom | |
| ZTE | |
| KPN |
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: #27 (Verified Caller), #35 (5G New Calling), #34 (Shutdown Service Status), #2 (Tenure)
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
- 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:
Recent Updates & Recap
TSC meeting 18th April:
- The subgroups/repos have been created:
- Network Access Management: CPE Management
- Location Insights: Most Frequent Location + Device Visit Location
- 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 e under discussion, some companies have commited to make a mor 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 there are approved. New PRs and Issues need to be opened in the new repo.
Codeowners:
Anyone else commits to be codeowner?
- Keep the pull request in the old repo and the new entering ones move them to the new repo
- Issues will be moved to the new repo
Backlog table
- Table updated in PR#38
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 |
| Open |
| 20240425-01 | API Backlog Governance | To include Chris as a Codeowner in the new API Backlog Repo | -- |
| Closed |
| 20240425-02 | Centillinon | Next API Backlog meeting, Nick to bring new use cases and endpoints | 351 |
| Open |
| 20240425-03 | China Telecom | Include in the template that the scope is not limited to mobile lines and the shared slides in the template as supporting documents | 409 |
| Open |
Discussion
Current Issues
The API template is available in PR#329
China Unicom and Telefonica to create a single family for both API: Location Insights, Use historical informations to manage location information of the user.
LOCATION INSIGHTS FAMILY:
- API de Device Visit Location (china unicom)
- Most Frequent Location (telefonica & TIM)
| 17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. |
The issue is not eligible to be closed yet. DECISION: not treated | 397 | Netfocusin Technologies | Does not seem to be in the Scope of Camara. DECISION: Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) | China Telecom | New API proposal: Verified Caller The API template is available in PR#410 Input from OGW Drop 4 | |
Deutsche Telekom | New API Proposal: Device Data Volume | The Template was merged by mistake PR#411, The PR needs to be updated The two APIs will be treated as new proposals that will be presented to the TSC when ready in BL ACTION: Reopen the closed pull request or make a new one with the existing files | -- | New API Proposal: Call Status |
Closing Issues
Nick will be working within next weeks on providing what camara can work on within this API ACTION: Next API Backlog, Nick will bring new use cases and endpoints | |||
| 4 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Ricardo is currently working on modeling a new table New WoW 3 companies needed Nick propose to focus more in the Commercial viability of the proposal in orther to rise up interest of other companies Huub points out the sensibility of posting commercial strategies within this type of forums as many companies are potential competitors 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 |
| 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 issue is not eligible to be closed yet. |
| 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 |
| 24 | Netfocusin Technologies | New Proposal: Steering of Roaming Management |
Input from OGW Drop 3
China Unicom and Telefonica to create a single family for both APIs: Location Insights, Use historical informations to manage location information of the user.
TIM is supporting Home Location Verification but changing the name so to reach a wider scope.LOCATION INSIGHTS FAMILY:
- API de Device Visit Location (china unicom)
- Most Frequent Location (telefonica & TIM)
Deutsche Telekom
Best Interconnection
The API template is available in PR#381
Input from OGW Drop 3
The issue was not treated in this conference call. Noel aplogized in advance and suggested to wait till April first week TSC meeting to move on with this API
DECISION: Move to TSC
Charter Communications
CPE management
The API template is available in PR#379. First YAML available here.
CPE Management API proposal was approved by TSC.
Ricardo has to provide the CODEOWNERS and initial MAINTAINERS to the TSC. This have been provided within Issue#378_comment
HomeDevicesQoD owners queried to have this API in a separated github project despite having regular meetings to align common terms (API Family). This involves having more than one CODEOWNER for this API (no further problem)
New github subproject to be created: Home Devices - Network Access Management
DECISION: GiutHub repo name approved
T-Mobile US
Does not seem to be in the Scope of Camara. DECISION: Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) | |||
China Telecom | New API proposal: Verified Caller The API template is available in PR#410 Input from OGW Drop 4 | Eric: Is the initial customer making a call to the API to show the brand to clients? Jason: Yes, it would be eg the hospital or the bank. Not limited to mobile lines. Start by API aproach and then include de registration flows and interworkings All the information need to be preprovided in the systems for the API to work (templates) Verified call can not be spufed or faked by criminals as there is the mobile number ACTION: Include in the template that the scope is not limited to mobile lines ACTION: Include the shared slides in the template as supporting documents | |
Deutsche Telekom | New API Proposal: Device Data Volume | The Template was merged by mistake PR#411, The PR needs to be updated The two APIs will be treated as new proposals that will be presented to the TSC when ready in BL ACTION: Reopen the closed pull request or make a new one with the existing files | |
-- | New API Proposal: Call Status | ||
Vodafone | New API Proposal: Tenure The API template is availale in PR#1 | ||
China Unicom | New API Proposal: The API tempate is available in PR#31 | ||
China Mobile | 5G New Calling The API template is available PR#31 |
Closing Issues
| 20 | Deutsche Telekom | Best Interconnection |
It was accepted by the TSC to treat this as a new API
intitial YAML files to be included in the API TEMPLATEPR#381 | The issue was not treated in this conference call |
Telefonica&DT
Scope Change: QoD API
The API template is available in PR#403
Noel: (mobileQoD to QoD change) Consider the combination or relationship between QoD and CPE/Home Devices subproject
Eric: (provision) difficult to ensure a pfile characteristic (throughput, latency) for a long time. Let's discuss in the subgroup.
Also, shall same mechanism apply to HomeQoD? to be brought tto Home QoD subgroup.
DECISION: Both approved
New Issues
Action Points
AP Owner
AP description
Related issue
Due date
Status
. Noel aplogized in advance and suggested to wait till April first week TSC meeting to move on with this API DECISION: Move to TSC | |||
| 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 |
| 5 | China Unicom | Device Visit Location | |
| 16 | Telefonica | Most Frequent Location | |
| 21 | Charter | CPE Management |
New Issues
Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
Decision Points
| DP # | DP description | Related issue |
AoB
Next Backlog conf. call: 9th May, 10-11 UTC+2.
Next TSC conf. call: 2nd May, 10-11,30 UTC+2
Q&A
How does CAMARA API pipeline work?
...