Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New API proposal- Device management #50

Open
maheshc01 opened this issue May 20, 2024 · 6 comments · May be fixed by #30
Open

New API proposal- Device management #50

maheshc01 opened this issue May 20, 2024 · 6 comments · May be fixed by #30
Labels
API Proposal enhancement New feature or request

Comments

@maheshc01
Copy link
Collaborator

Related to PR #30

Device management was identified as priority API as part of OGW drop 2.
The API will focus on managing device subscription state . Initial scope to include add, activate, suspend, restore, deactivate and delete.
Additional information is available as part of the PR.

@maheshc01 maheshc01 added the enhancement New feature or request label May 20, 2024
@maheshc01 maheshc01 linked a pull request May 20, 2024 that will close this issue
@TEF-RicardoSerr TEF-RicardoSerr linked a pull request May 21, 2024 that will close this issue
@maheshc01
Copy link
Collaborator Author

Hi @TEF-RicardoSerr I havent been able to join the API backlog call.I will plan on joining the call on 27th of this month.
Are we waiting on additional supporting operators to take this API to TSC or anything else pending on this?

@gmuratk
Copy link
Collaborator

gmuratk commented Oct 29, 2024

I wanted to ask a question based on what was presented in the API Backlog Meeting on October 24, 2024. Doesn't the scope of the feature(s) proposed fall in to Operate API?

@maheshc01
Copy link
Collaborator Author

Hi @gmuratk, IoT has been recognized as a family of APIs for CAMARA to support under GSMA Opengateway and this proposal provides basic set of capabilities for IoT device mgmt. This API will still falls in the category of northbound APIs as is the case for all CAMARA APIs. One uniqueness i like to note for this family of APIs is that rather than ASPs being the predominant users as in the case for other CAMARA APIs thus far, this API would be more widely used by enterprise customers (small/medium/large) in my opinion.
Focus of Operate APIs is quite different to what is proposed here. Operate APIs cater to standardizing the developer engagement and experience in terms of registration and accessing the APIs, inventory of the APIs, monitoring the utilizations, billing etc

Hope this helps.
would like to hear back on your thoughts and other's opinion as well on this.

@gmuratk
Copy link
Collaborator

gmuratk commented Oct 29, 2024

Hi @maheshc01,
I have no arguments against IoT being in the scope. The reason I raised the question is mainly due to proposed capabilities.

@maheshc01
Copy link
Collaborator Author

IoT Provisioning APIs.pdf

@gmuratk The PR which has the slides i shared during the call is not approved yet. Reattaching it again here for reference.
the scope identified for the API in the proposal covers add, activate, suspend, restore, deactive and delete in the context of device mgmt.
Could you elaborate further on what you mean by these capabilities falling in the scope of operate APIs?

@gmuratk
Copy link
Collaborator

gmuratk commented Oct 29, 2024

@maheshc01 thanks for sharing the slides. For example, capabilities for Adding devices and Activating service may have an overlap with service provisioning that is listed as part of 'Operate API' scope in CAMARA Project Charter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Proposal enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants