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

Scope Enhancement: network info for Device Status API Family #66

Closed
Kevsy opened this issue Jul 16, 2024 · 6 comments · Fixed by #72
Closed

Scope Enhancement: network info for Device Status API Family #66

Kevsy opened this issue Jul 16, 2024 · 6 comments · Fixed by #72
Labels
enhancement New feature or request

Comments

@Kevsy
Copy link
Contributor

Kevsy commented Jul 16, 2024

API Scope Enhancement

Field Description
API name DeviceStatus
New API name NetworkInfo
Scope Enhancement owner Vodafone
Scope Enhancement summary Read-only API to return the name of the operator and network type for an identified network-connected device. Business cases (1) developers can account for the different behaviours they have historically encountered from different network operators (2) developers can determine if the connection is to a virtual operator, which may result in different network capabilities (3) knowing the type of the network the device is connected to (cellular network type, fixed/Wi-Fi, satellite) allows the developer to better estimate network stability. Overall each business case can help improve end user experience
Technical viability Operator name is static, connection type is available from via NEF.
Commercial viability Server implementations not known - but MNC/MCC lookup available on the UE via programmatic lookup to OS libraries.
YAML code available? YES
Validated in lab/productive environments? NO.
Validated with real customers? NO.
Validated with operators? NO.
Supporters in API Backlog Working Group Vodafone, Deutsche Telekom
@Kevsy Kevsy added the enhancement New feature or request label Jul 16, 2024
@Kevsy
Copy link
Contributor Author

Kevsy commented Jul 16, 2024

Submitted as per action from API Backlog call 11th July

@NoelWirzius please let me know any changes needed

@NoelWirzius
Copy link
Collaborator

@Kevsy lgtm
@gmuratk would be great if you compare this to your proposal in Device Status

Kevsy added a commit to Kevsy/APIBacklog that referenced this issue Jul 30, 2024
@jgarciahospital
Copy link
Collaborator

As discussed in #72 (comment), pending to clarify final destination of the proposal

@gmuratk
Copy link
Collaborator

gmuratk commented Sep 10, 2024

@Kevsy lgtm @gmuratk would be great if you compare this to your proposal in Device Status

@NoelWirzius I think it is aligned with the proposal previously submitted to Device Status. As for consideration in #72, I think it will be beneficial to keep this as a separate API rather than enhancing Reachability Status API.

@Kevsy
Copy link
Contributor Author

Kevsy commented Sep 12, 2024

HI @NoelWirzius - please can you advise regarding the status of this enhancement, does the Device Status team believe it should be a separate API in the family? Many thanks!

@Kevsy
Copy link
Contributor Author

Kevsy commented Sep 24, 2024

Please can the team advise whether this capability to provide more granular data connection information (2G/3G/4G/5G/Wi-Fi etc. plus MNO/MNC/operator identifier) should be a separate API within the Device Status family, or a scope enhancement to extend CONNECTED_DATA?

This topic relates to open issue 66 and PR 72 in APIBacklog , so your decision much appreciated :)

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

Successfully merging a pull request may close this issue.

4 participants