This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 60
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0eaa76f
commit 3c8d1fa
Showing
1 changed file
with
10 additions
and
0 deletions.
There are no files selected for viewing
10 changes: 10 additions & 0 deletions
10
...og/documentation/SupportingDocuments/API proposals/APIproposal_Device_Volume.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
| **Field** | Description | | ||
| ---- | ----- | | ||
| API family name |Device Data Volume | | ||
| API family owner | Deutsche Telekom (Noel Wirzius)| | ||
| API summary | This API offers detailed insights into the customer's data usage status, including whether they have remaining data volume available and their current position within that volume allocation. It accurately determines whether the customer is nearing the beginning or the end of their allocated data volume, providing valuable information for managing data usage efficiently.| | ||
| Technical viability | The API should get information for a dedicated Sim-Card and also offer this in a subscription mode. The return value should not be a fixed value more an estimated indicator (e.g. <200mb, <1Gb ...) | | ||
| Commercial viability | This API was requested by different content providers. It helps them to get more insights, how to deliver their traffic. | NO | | ||
| Validated in lab/productive environments? | Yes | | ||
| Validated with operators? | Yes | | ||
| Supporters in API Backlog Working Group | | |