From b3bc7cfeb6c1598d2581795183c0274bd3a06733 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Wed, 5 Nov 2025 16:15:35 +0100 Subject: [PATCH 01/10] Add API Scope Enhacement for Consent Info Evolution --- ...ment_Consent_Info_Controlled_Delegation.md | 53 +++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md diff --git a/documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md b/documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md new file mode 100644 index 0000000..581624a --- /dev/null +++ b/documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md @@ -0,0 +1,53 @@ +# API Scope Enhancement Template + +This template captures all the information that a partner should fill out when proposing a scope enhancement for an existing CAMARA API. + +## API name +[Consent Info](https://github.com/camaraproject/IdentityAndConsentManagement/tree/main) + +## New API name +No new name proposed at this stage. The enhancement is considered an evolution of the existing Consent Info API or could be a new API, to be decided during design phase. + +## Scope Enhancement owner +Telefónica + +## Scope Enhancement summary +This scope enhancement aims to extend the capabilities offered by the existing **Consent Info API** to support a more flexible and user-friendly mechanism for **consent capture**, referred to as controlled delegation. + +Under the current implementation, the end-user provides consent directly through operator-managed channels or web interfaces. The proposed enhancement introduces the possibility for **trusted developers or aggregators** to present the consent interface within their own applications, using the consent texts and parameters provided by the operator. + +The operator remains fully responsible for consent registration, storage, and lifecycle management (including audit, traceability, and opt-out). The enhancement focuses on improving user experience and enabling new types of consent-driven interactions while maintaining operator control and compliance with privacy regulations. + +**In-scope business cases include**: +- **App managed UX consent capture**: Developers collect end-user consent within their own app, their own look&feel and being free to choose the best moment to collect it by using operator-provided texts to later submit the use’s response. +- **Integrated onboarding**: Consent capture is embedded within customer registration, verification flows or any other flow the developer may find most suitable, avoiding redirections to external operator portals. +- **Consent renewal campaigns**: Applications can trigger consent renewal campaigns in their own interface while ensuring operator-level registration. + +## Technical viability +The proposed enhancement builds upon the existing Consent Info framework and its relationship with operator consent management systems. + +It reuses the existing operator infrastructure (Consent Master) for consent validation, registration, and transparency, while adding a new controlled mechanism for capturing consent externally via developer applications. + +Further analysis is ongoing regarding the secure identification and authentication of the subscriber during delegated consent capture. The proposal does not depend on any new 3GPP or TMForum feature, but aligns conceptually with identity and privacy control principles under development in the ICM scope. + +## Commercial viability +The enhancement responds to developer and enterprise demand for smoother consent collection processes and reduced user friction in digital journeys. + +It also aligns with current commercial deployments of consent management systems across operators, which can be extended to support delegated consent registration. + +Several operators are already evaluating integration with trusted developers and aggregators under privacy-compliant frameworks. No dependency on commercial third-party technology is identified at this stage. + +## YAML code available? +NO + +## Validated in lab/productive environments? +Initial feasibility assessments and simulated flows have been conducted internally to validate integration feasibility with operator consent managers. + +## Validated with real customers? +Evaluation with selected customers is planned after initial review and alignment across operators. + +## Validated with operators? +To be validated. + +## Supporters in API Backlog Working Group +To be confirmed. From 56ee31fea0ac6ea673be648bd5af756ced2bd090 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Tue, 25 Nov 2025 11:38:27 +0100 Subject: [PATCH 02/10] Update backlog table with the changes through December --- documentation/APIbacklog.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index 1d3c377..a377eca 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -987,12 +987,12 @@ This is a live doc that captures the status of all the APIs which have been form - IMEI Fraud + DeviceAuthenticity (previously IMEI Fraud) xFlow Research Inc*
xFlow Research Inc
Template
2023/08/13
- + N/A N/A @@ -1002,7 +1002,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2024/11/26
- + N/A N/A @@ -1026,6 +1026,16 @@ This is a live doc that captures the status of all the APIs which have been form N/A N/A + + Radio Signal Attenuation + Ericsson*
+ + Template
2025/10/20
+ + + N/A + N/A + Consent and Measurement Centillion*
Centillion
From 375e53ac377cc15833ff649379f502bdfc541ed7 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Tue, 25 Nov 2025 11:40:58 +0100 Subject: [PATCH 03/10] Delete documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md --- ...ment_Consent_Info_Controlled_Delegation.md | 53 ------------------- 1 file changed, 53 deletions(-) delete mode 100644 documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md diff --git a/documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md b/documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md deleted file mode 100644 index 581624a..0000000 --- a/documentation/API proposals/API-Scope_Enhancement_Consent_Info_Controlled_Delegation.md +++ /dev/null @@ -1,53 +0,0 @@ -# API Scope Enhancement Template - -This template captures all the information that a partner should fill out when proposing a scope enhancement for an existing CAMARA API. - -## API name -[Consent Info](https://github.com/camaraproject/IdentityAndConsentManagement/tree/main) - -## New API name -No new name proposed at this stage. The enhancement is considered an evolution of the existing Consent Info API or could be a new API, to be decided during design phase. - -## Scope Enhancement owner -Telefónica - -## Scope Enhancement summary -This scope enhancement aims to extend the capabilities offered by the existing **Consent Info API** to support a more flexible and user-friendly mechanism for **consent capture**, referred to as controlled delegation. - -Under the current implementation, the end-user provides consent directly through operator-managed channels or web interfaces. The proposed enhancement introduces the possibility for **trusted developers or aggregators** to present the consent interface within their own applications, using the consent texts and parameters provided by the operator. - -The operator remains fully responsible for consent registration, storage, and lifecycle management (including audit, traceability, and opt-out). The enhancement focuses on improving user experience and enabling new types of consent-driven interactions while maintaining operator control and compliance with privacy regulations. - -**In-scope business cases include**: -- **App managed UX consent capture**: Developers collect end-user consent within their own app, their own look&feel and being free to choose the best moment to collect it by using operator-provided texts to later submit the use’s response. -- **Integrated onboarding**: Consent capture is embedded within customer registration, verification flows or any other flow the developer may find most suitable, avoiding redirections to external operator portals. -- **Consent renewal campaigns**: Applications can trigger consent renewal campaigns in their own interface while ensuring operator-level registration. - -## Technical viability -The proposed enhancement builds upon the existing Consent Info framework and its relationship with operator consent management systems. - -It reuses the existing operator infrastructure (Consent Master) for consent validation, registration, and transparency, while adding a new controlled mechanism for capturing consent externally via developer applications. - -Further analysis is ongoing regarding the secure identification and authentication of the subscriber during delegated consent capture. The proposal does not depend on any new 3GPP or TMForum feature, but aligns conceptually with identity and privacy control principles under development in the ICM scope. - -## Commercial viability -The enhancement responds to developer and enterprise demand for smoother consent collection processes and reduced user friction in digital journeys. - -It also aligns with current commercial deployments of consent management systems across operators, which can be extended to support delegated consent registration. - -Several operators are already evaluating integration with trusted developers and aggregators under privacy-compliant frameworks. No dependency on commercial third-party technology is identified at this stage. - -## YAML code available? -NO - -## Validated in lab/productive environments? -Initial feasibility assessments and simulated flows have been conducted internally to validate integration feasibility with operator consent managers. - -## Validated with real customers? -Evaluation with selected customers is planned after initial review and alignment across operators. - -## Validated with operators? -To be validated. - -## Supporters in API Backlog Working Group -To be confirmed. From 8b5279ca6f813061ac51eec64ae610a9da9fdc55 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Thu, 4 Dec 2025 10:36:54 +0100 Subject: [PATCH 04/10] Add repo for esimremotemanagement and deviceauthenticity --- documentation/APIbacklog.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index a377eca..57526d0 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -929,8 +929,11 @@ This is a live doc that captures the status of all the APIs which have been form Template
2024/11/26
-
  • TSC Approved (2025/03/20) and Onboarding
- Pending +
  • TSC Approved (2025/03/20)
+ + eSimRemoteManagement + Maintainers + N/A @@ -993,7 +996,10 @@ This is a live doc that captures the status of all the APIs which have been form Template
2023/08/13
  • TSC Approved (2025/11/20)
- N/A + + DeviceAuthenticity + Maintainers + N/A @@ -1003,7 +1009,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2024/11/26
  • TSC Approved (2025/10/02) & Onboarding under GSMA (2025/11/25)
- N/A + Pending N/A From 3a9e48298d41d36041813ef3e9e2baebbaae79c3 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Thu, 18 Dec 2025 21:54:59 +0000 Subject: [PATCH 05/10] add group management api and 18 dec TSC --- documentation/APIbacklog.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index 57526d0..37f4ba4 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -1012,13 +1012,23 @@ This is a live doc that captures the status of all the APIs which have been form Pending N/A + + Radio Signal Strength + Ericsson*
+ + Template
2025/10/20
+ +
  • TSC Approved (2025/12/18)
+ N/A + N/A + In Home Device Management API Infosys*
Template
2025/08/09
-
  • Under backlog discussion
+
  • TSC Approved (2025/12/18)
N/A N/A @@ -1033,10 +1043,10 @@ This is a live doc that captures the status of all the APIs which have been form N/A - Radio Signal Attenuation - Ericsson*
+ Group Management API + T-Mobile US*
- Template
2025/10/20
+ Template
2025/12/17
  • Under backlog discussion
N/A From 3ea6de2549bd0ca15768232e2d055ac42ab4fa24 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Mon, 22 Dec 2025 08:39:47 +0000 Subject: [PATCH 06/10] add consent management --- documentation/APIbacklog.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index 37f4ba4..cc88b16 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -1032,6 +1032,19 @@ This is a live doc that captures the status of all the APIs which have been form N/A N/A + + Consent Management API + Telefónica*
+ + Template
2025/11/05
+ +
  • TSC Approved (2025/12/18)
+ + ConsentManagement + Maintainers + + N/A + Voice One Time Password Call Heksagon*
From e4cd300414716a63fa4e1be6be2880b8efcd0dc7 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Mon, 22 Dec 2025 08:41:13 +0000 Subject: [PATCH 07/10] add onboarding --- documentation/APIbacklog.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index cc88b16..c918825 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -1018,7 +1018,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2025/10/20
-
  • TSC Approved (2025/12/18)
+
  • TSC Approved & Onboarding (2025/12/18)
N/A N/A @@ -1028,7 +1028,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2025/08/09
-
  • TSC Approved (2025/12/18)
+
  • TSC Approved & Onboarding (2025/12/18)
N/A N/A @@ -1038,7 +1038,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2025/11/05
-
  • TSC Approved (2025/12/18)
+
  • TSC Approved & Onboarding (2025/12/18)
ConsentManagement Maintainers From 6413925f9fc41d7714f1341ad0bcbb126b9d3e28 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Mon, 22 Dec 2025 09:46:39 +0100 Subject: [PATCH 08/10] Update documentation/APIbacklog.md --- documentation/APIbacklog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index c918825..fdbcdfb 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -929,7 +929,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2024/11/26
-
  • TSC Approved (2025/03/20)
+
  • TSC Approved (2025/03/20) & Onboarding (2025/03/24)
eSimRemoteManagement Maintainers From 2848a44e45de8b7dd0b0e153b4649ce5449bd8bd Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Mon, 22 Dec 2025 16:28:16 +0000 Subject: [PATCH 09/10] Add TrustWorthiness Intent API --- documentation/APIbacklog.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index fdbcdfb..6445335 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -1065,6 +1065,16 @@ This is a live doc that captures the status of all the APIs which have been form N/A N/A + + TrustWorthiness Intent API + National Centre for Scientific Research Demokritos (NCSRD), Infolysis S.A*
+ + Template
2025/12/22
+ +
  • Under backlog discussion
+ N/A + N/A + Consent and Measurement Centillion*
Centillion
From 527a490159c05983c528ba2ea9671bdf3257a217 Mon Sep 17 00:00:00 2001 From: Alberto Ramos Monagas Date: Wed, 7 Jan 2026 11:25:35 +0100 Subject: [PATCH 10/10] Apply suggestion from @albertoramosmonagas --- documentation/APIbacklog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/APIbacklog.md b/documentation/APIbacklog.md index 6445335..088e9e8 100644 --- a/documentation/APIbacklog.md +++ b/documentation/APIbacklog.md @@ -1009,7 +1009,7 @@ This is a live doc that captures the status of all the APIs which have been form Template
2024/11/26
  • TSC Approved (2025/10/02) & Onboarding under GSMA (2025/11/25)
- Pending + Under GSMA N/A