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

Questions over HomeDeviceQoD #52

Closed
ShutingQing opened this issue Jul 29, 2023 · 2 comments
Closed

Questions over HomeDeviceQoD #52

ShutingQing opened this issue Jul 29, 2023 · 2 comments

Comments

@ShutingQing
Copy link
Collaborator

Dears, I have a question over this API, may someone know the answer? Can app, the api caller, knows which router is the user's router? Or how should app know the devices that the user is allowed to adjust the bandwidth?

@jpengar
Copy link
Collaborator

jpengar commented Jul 31, 2023

Dears, I have a question over this API, may someone know the answer? Can app, the api caller, knows which router is the user's router? Or how should app know the devices that the user is allowed to adjust the bandwidth?

@ShutingQing Please refer to:

- The operation is executed for the user whose `sub` is in the access token used to call this endpoint, and for the home network also deducted from the information included in the access token.

This API has been designed with the expectation that the API client has previously obtained a 3-legged access token that gives access to the appropriate scope of this API (home-devices-qod-qos-write) according to the CAMARA Authentication/Authorisation API access mechanisms.

As part of the procedures to obtain an access token, the user and the home network are identified and authenticated (typically using network-based authentication on the telco side, based on the observed public API of the device, which would be the public IP of the home router).

Thus, the API request includes an access token associated with the user (standard sub field in the access token) and the Internet identifier corresponding to the home network to which the device is connected. So the user's information (the telco subscriber and resource owner) and the user's home network information are deducted from the access token.

And the target user device is identified by the internal IP address (ipAddress field in the API request body) of that device in the home network.

@jpengar
Copy link
Collaborator

jpengar commented Aug 25, 2023

I'm closing this issue since there have been no further comments and it has already been clarified how the user's router and home device are identified.

@jpengar jpengar closed this as completed Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants