Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

Avoid telco specific terminology in APIs #108

Closed
RandyLevensalor opened this issue Dec 9, 2022 · 2 comments · Fixed by #120
Closed

Avoid telco specific terminology in APIs #108

RandyLevensalor opened this issue Dec 9, 2022 · 2 comments · Fixed by #120

Comments

@RandyLevensalor
Copy link

There appears to be a preference to using mobile / 3GPP specific terminology for the APIs. This makes it confusing for adding wireline networks. Plus API consumers may not be familiar with 3GPP terminology.

One example is using UE to describe a user device. This is included in the commonalities documentation and the QualityOnDemand API.

Moving to something access network independent could improve the clarity of the APIs for the API consumers and wireline providers. Instead of UE, we could use device, user device, or target device for managing the local device. This would also preclude a SIM as a part of the northbound APIs.

@shilpa-padgaonkar
Copy link
Contributor

@RandyLevensalor #120 has been created to address the issue. You are welcome to contribute.

@shilpa-padgaonkar shilpa-padgaonkar changed the title Avoid mobile specific terminology in APIs Avoid telco specific terminology in APIs Jan 18, 2023
@shilpa-padgaonkar
Copy link
Contributor

As there are individual issues for subproject created, this issue will be closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants