...
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 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. 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 the DeviceStatus family and separate repositories (deviceStatus) → Device Data Volume | |
Rogers | New API Proposal: Call Status | DECISION 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 |
...
Issue | Owner | API | Repository |
China Telecom | Verified Caller | VerifiedCaller | |
Vodafone | Tenure | Tenure |
...
New Issues
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 |
...
DP # | DP description | Related issue |
20240523-01 | 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 | |
20240523-03 | Call Status API proposal overlaped with existing CAMARA projects and owner REDACTED Issue. Issue is closed |
AoB
Next Backlog conf. call: 23th May13th June, 1510-1611 UTC+2.
Next TSC conf. call: 06th June, 10-11,30 UTC+2
...