Sponsored DATA Api - New API Request #223.- #224
Conversation
Adding Sponsored Data API proposal - Telecom Argentina
jafilippini1
requested review from
Noel-Wirzius-DT,
caubut-charter,
eric-murray and
jgarciahospital
as code owners
|
Hi @jafilippini1, before attending the API backlog WG meeting and submitting the API, please check for the “is not authorized under a signed CLA” error. Just click on the link to verify yourself as a user. |
| | API family name | Sponsored Data | | ||
| | API family owner | Telecom Argentina S.A. | | ||
| | API summary | The Sponsored Data API enables enterprises to sponsor mobile data traffic for specific subscribers, allowing them to access the internet or use applications without consuming their own data allowance.<br><br>This first version of the API is designed for ANY-destination sponsorship, meaning all traffic generated by the user during a sponsorship session is zero-rated. This approach ensures simple implementation and broad applicability across diverse use cases.<br><br>Sponsorship applies to a predefined volume of traffic and for a determined time period, ensuring controlled usage according to the campaign parameters.<br><br>The API may be extended in future iterations to support targeted sponsorship by destination (e.g., domain, IP, service), allowing operators to restrict sponsorship to specific digital services. | | ||
| | Technical viability | This initial version of the Sponsored Data API is technically viable in networks that support the provisioning of secondary data offers (Free Units) with zero rating through the Online Charging System (OCS).<br><br>The implementation assumes a sponsorship model based on ANY-destination, meaning no DPI or destination-specific control is required. Therefore:<br><br>The API only requires that the OCS can handle multiple concurrent data balances per subscriber, and apply 0-rating to the sponsored volume.<br><br>Real-time enforcement of the Free Unit usage is handled mainly by the OCS, without the need for complex or customized PCRF/PCF rules.<br><br>An internal API Gateway (APIGW) interfaces with the OCS to initiate and revoke the sponsored offer using secure APIs.<br><br>The solution is compatible with 3GPP Rel-13 and above, assuming basic support for OCS-based data rating and quota management. |
There was a problem hiding this comment.
Let's avoid such technical language, I invite you to review the description and if we use acronyms, define them before, for example, in this context, what is DPI?
There was a problem hiding this comment.
Hi Alberto,
Thanks for your comments.
I have a quick question: since I’m contributing with this proposal on behalf of Telecom Argentina, I assume I need to be authorized as a Corporate CLA Contributor, right? Or would it also be valid to sign as an Individual Contributor, even if I’m representing Telecom?
Also, regarding your feedback on the document I uploaded, I understand your comments — I’ll revise it to remove the technical jargon and ensure all acronyms are defined before use.
Lastly, I’ll upload the API’s YAML file to the “documentation” repository from my side, so everything is ready to move forward as soon as I’m authorized under the CLA.
Thanks again.
Julián
There was a problem hiding this comment.
since I’m contributing with this proposal on behalf of Telecom Argentina, I assume I need to be authorized as a Corporate CLA Contributor, right? Or would it also be valid to sign as an Individual Contributor, even if I’m representing Telecom?
@jafilippini1 Your assumption is correct, you have to be covered under a CCLA, afaik Linux Foundation is not accepting ICLA for accounts which are affiliated with a company. If you have further questions about EasyCLA you can contact the LF team via support@camaraproject.org (cc: @wrathwolf)
Section Technical viability was modified taking off technical terms. Related to issue camaraproject#223
|
Hi @jafilippini1, I just wanted to check if you or someone of Telecom Argentina is planning to join one of the upcoming backlog sessions to present the Sponsored DATA API. Since it was first proposed, we’ve already had two sessions, so it would be great if you could come by and share it with the other telcos. |
|
Hi @albertoramosmonagas, thanks for your message. |
Great, in theory the CLA is for the PRs and any code you plan to upload to GitHub. To access the backlog meetings, you just need to use this link: Meeting Cadence:
The next meetings are on July 10 and July 24. Regarding the template, there isn’t any specific one—you can simply use whatever you have internally to present the scope of this API. We are here for you! |
If you would like to use a neutral powerpoint template from CAMARA you can go with this one: https://github.com/camaraproject/Marketing/blob/main/documentation/MarketingMaterial/CAMARA%20Master%20Template.potx. But as @albertoramosmonagas already wrote, there is no need to use it. |
|
Hi Alberto and Herbert, Thank you for your response. We are planning to present the scope of our API proposal on July 10, if that date is still available. Could you please confirm if it works for you? Also, should we send our presentation in advance to someone to be included in a larger deck, or will we present it directly from our own laptops on that day? Lastly, we understand that we can join directly using the provided link, without any prior registration. Could you please confirm this as well? Best regards, |
Hello! great, backlog meetings are recurring every two weeks. If they are recorded in these meetings they are automatically triggered and always (as long as nothing unusual happens) will be done. So there is no problem with you presenting the API on July 10. Regarding the presentation, having it uploaded in the Proposal PR would be enough, but it can be uploaded after submitting the API in the backlog meeting. On that day it would be enough to submit it directly from your own laptops. To join the session is by zoom. Once you are registered you should not encounter any problems. However, you can join 10 minutes before the session to test that everything works correctly. Best regards |
|
Hi Alberto, |
Great, see you on Thursday 10th at the backlog meeting, that's all it takes. Thank you very much for your response. Try to fix the EasyCLA in view of the meeting, which is the first item to come out of the session! Thanks! |
|
Hi Alberto, Thanks for your response. Understood — we’ll proceed to sign the CLA in the coming days, and will reschedule our presentation for after that step. Best regards, |
|
Hi team, |
|
Hi team, |
Hi team, Here is the "Sponsor_Data_API.v1.yaml" file for reference. Thanks, Julián
Hi team, Here is the "Sponsored Data API" PowerPoint presentation file for reference. Thanks, Julián
|
Hi team, |
|
Hi @Noel-Wirzius-DT @caubut-charter @eric-murray @jgarciahospital, |
6 participants
Adding Sponsored Data API proposal - Telecom Argentina
New API Proposal: #223
Which issue(s) this PR fixes:
Fixes #223