generated from camaraproject/Template_API_Repository
-
Notifications
You must be signed in to change notification settings - Fork 31
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from maheshc01/maheshc01-patch-1
Create APIproposal_DeviceManagement_Verizon.md
- Loading branch information
Showing
1 changed file
with
11 additions
and
0 deletions.
There are no files selected for viewing
11 changes: 11 additions & 0 deletions
11
documentation/API proposals/APIproposal_DeviceManagement_Verizon.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,11 @@ | ||
| Field | Description | | ||
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | ||
| API family name | Device Management API family | | ||
| API family owner | Verizon | | ||
| API summary | Manage device subscription state . Initial scope to include add, activate,suspend, restore, deactive and delete. | | ||
| Technical viability | These APIs are applicable for 3G, 4G and 5G devices and not dependent on specific network functions or cloud capabilities | | ||
| Commercial viability | Developed and owned by Verizon and commercially available in Verizon’s network | | ||
| YAML code available? | YES | | ||
| Validated in lab/productive environments? | YES. Verizon’s production network in the United States | | ||
| Validated with real customers? | YES. customers currently use these APIs to manage their devices | | ||
| Validated with operators? | List of supporters.<br>NOTE: That shall be added by the Working Group. | |