From 9709cc367395fa7d07d33b70da0e161f376bcebf Mon Sep 17 00:00:00 2001 From: Kevin Smith Date: Tue, 30 Jul 2024 15:49:11 +0100 Subject: [PATCH 1/3] Create APIScopeEnhancement_Device_Status_network_info Originally submitted as issue #66 --- ...APIScopeEnhancement_Device_Status_network_info | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 documentation/API proposals/APIScopeEnhancement_Device_Status_network_info diff --git a/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info b/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info new file mode 100644 index 0000000..2d99035 --- /dev/null +++ b/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info @@ -0,0 +1,15 @@ +# API Scope Enhancement + +| **Field** | Description | +| ---- | ----- | +| API name | [DeviceStatus](https://github.com/camaraproject/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 | From 001a003afbbf1a1ed83986fddc32a74068723399 Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Tue, 30 Jul 2024 16:58:25 +0200 Subject: [PATCH 2/3] Including file extension --- ...ork_info => APIScopeEnhancement_Device_Status_network_info.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename documentation/API proposals/{APIScopeEnhancement_Device_Status_network_info => APIScopeEnhancement_Device_Status_network_info.md} (100%) diff --git a/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info b/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info.md similarity index 100% rename from documentation/API proposals/APIScopeEnhancement_Device_Status_network_info rename to documentation/API proposals/APIScopeEnhancement_Device_Status_network_info.md From 57d3a3254774c6412811c36212aae4598d359d09 Mon Sep 17 00:00:00 2001 From: Kevin Smith Date: Fri, 27 Sep 2024 16:49:07 +0100 Subject: [PATCH 3/3] Update APIScopeEnhancement_Device_Status_network_info.md Amended per API Backlog/Device Status discussion (ref Device Status [PR 158](https://github.com/camaraproject/DeviceStatus/pull/158) --- .../APIScopeEnhancement_Device_Status_network_info.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info.md b/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info.md index 2d99035..d76cc64 100644 --- a/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info.md +++ b/documentation/API proposals/APIScopeEnhancement_Device_Status_network_info.md @@ -3,11 +3,11 @@ | **Field** | Description | | ---- | ----- | | API name | [DeviceStatus](https://github.com/camaraproject/DeviceStatus) | -| New API name | NetworkInfo | +| New API name | ConnectedNetworkType | | 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.| +| Scope Enhancement summary | Read-only API to return the network type for an identified network-connected device. Business case: (1) knowing the type of the network the device is connected to (e.g cellular network type, fixed/Wi-Fi, satellite) allows the developer to better estimate network stability. | +| Technical viability | Connection type is available from via NEF. +| Commercial viability | Server implementations not known - but 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.|