From 13003d3ec1e051aa1ac7c69d6fd3595a0dfb324a Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Sat, 28 Oct 2023 12:48:10 +0200 Subject: [PATCH 1/6] Add files via upload --- ...sal_DynamicPeopleDensityInformation_Telefonica.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md diff --git a/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md b/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md new file mode 100644 index 00000000..54f07e49 --- /dev/null +++ b/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md @@ -0,0 +1,12 @@ +| **Field** | Description | +| ---- | ----- | +| API family name | Dynamic People Density Information | +| API family owner | Telefonica | +| API summary | The service enables developers with the capability to get dynamic population density data in a specific area for a future date&time, considering anonymized information of the network connected devices in the requested area at the flight time.
Use Case (1): Providing BVLOS flight the data to meet SORA 2.5 requirements in terms of intrinsic Ground Risk Class (iGRC).
Use Case (2): Providing data to identify if the ground risk class for a given drone flight is acceptable for the time of the flight, or an alternative time should be considered to lower the risk.
Service Inputs: Area of the flight (delimited space).
Service Outputs: maximum population density value for the given area. | +| Technical viability | The viability has been checked and it is based on providing the amount of people on a flight path obtained by aggregating number of SIMs connected to each antenna on the path and without considering M2M SIMs, extrapolating to real-desnsity of population based on tht level of radio occupancy. No individual subscriber data will be delivered as the information will be anonymized. | +| Commercial viability | For use in drone flight scenarios, where population density is required to ensure a secure level of risk | +| YAML code available? | NO
To be provided | +| Validated in lab/productive environments? | NO | +| Validated with real customers? | NO | +| Validated with operators? | YES
Proposal validates in OGW drop3 | +| Supporters in API Backlog Working Group | Telefonica; China Unicom (To align with RegionUserCount API) | \ No newline at end of file From 7efbb3dec6f66acf64f15ab391d299e6f35af148 Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Sat, 28 Oct 2023 12:57:35 +0200 Subject: [PATCH 2/6] Update APIBacklog.md --- APIBacklog/documentation/APIBacklog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/APIBacklog/documentation/APIBacklog.md b/APIBacklog/documentation/APIBacklog.md index f1258690..74af23f8 100755 --- a/APIBacklog/documentation/APIBacklog.md +++ b/APIBacklog/documentation/APIBacklog.md @@ -32,7 +32,7 @@ | IMEI Fraud | MTN | 2023/08/13| [Link](https://github.com/camaraproject/WorkingGroups/pull/277) | MTN, GSMA Open Gateway, Huawei | YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | | WebRTC | Telefónica | 2023/08/16| [Link]([https://github.com/camaraproject/WorkingGroups/pull/280](https://github.com/camaraproject/WorkingGroups/blob/main/APIBacklog/documentation/SupportingDocuments/API%20proposals/APIproposal_WebRTC_Telefonica.md)) | Telefónica, Mavenir, Orange, Vodafone, TMUS | YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | | Network Insights | Verizon | 2023/08/31| [Link](https://github.com/camaraproject/WorkingGroups/pull/295) | Verizon, 5GFF, GSMA Open Gateway| YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | - + | Dynamic People Density Information | Telefonica | Under Evaluation | Under Evaluation | Telefonica, GSMA Open Gateway| YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | ## Attributes - `API [family] name`: it is the name of the API [family] proposal From 67af59ff4b6412f50167c904d9c482e7c5a7563a Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Sat, 28 Oct 2023 14:59:57 +0200 Subject: [PATCH 3/6] Update APIBacklog.md --- APIBacklog/documentation/APIBacklog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/APIBacklog/documentation/APIBacklog.md b/APIBacklog/documentation/APIBacklog.md index 74af23f8..6cb598b5 100755 --- a/APIBacklog/documentation/APIBacklog.md +++ b/APIBacklog/documentation/APIBacklog.md @@ -32,7 +32,7 @@ | IMEI Fraud | MTN | 2023/08/13| [Link](https://github.com/camaraproject/WorkingGroups/pull/277) | MTN, GSMA Open Gateway, Huawei | YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | | WebRTC | Telefónica | 2023/08/16| [Link]([https://github.com/camaraproject/WorkingGroups/pull/280](https://github.com/camaraproject/WorkingGroups/blob/main/APIBacklog/documentation/SupportingDocuments/API%20proposals/APIproposal_WebRTC_Telefonica.md)) | Telefónica, Mavenir, Orange, Vodafone, TMUS | YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | | Network Insights | Verizon | 2023/08/31| [Link](https://github.com/camaraproject/WorkingGroups/pull/295) | Verizon, 5GFF, GSMA Open Gateway| YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | - | Dynamic People Density Information | Telefonica | Under Evaluation | Under Evaluation | Telefonica, GSMA Open Gateway| YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | + ## Attributes - `API [family] name`: it is the name of the API [family] proposal From f6c1e6fc087b56f8e9ed0ee50f382c61bf2ffeb0 Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Sat, 28 Oct 2023 15:00:25 +0200 Subject: [PATCH 4/6] Update APIBacklog.md From ab7846eb155de2acd2eff797d9fb4bb672847150 Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Sat, 28 Oct 2023 15:00:47 +0200 Subject: [PATCH 5/6] Update APIBacklog.md --- APIBacklog/documentation/APIBacklog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/APIBacklog/documentation/APIBacklog.md b/APIBacklog/documentation/APIBacklog.md index 6cb598b5..f1258690 100755 --- a/APIBacklog/documentation/APIBacklog.md +++ b/APIBacklog/documentation/APIBacklog.md @@ -32,7 +32,7 @@ | IMEI Fraud | MTN | 2023/08/13| [Link](https://github.com/camaraproject/WorkingGroups/pull/277) | MTN, GSMA Open Gateway, Huawei | YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | | WebRTC | Telefónica | 2023/08/16| [Link]([https://github.com/camaraproject/WorkingGroups/pull/280](https://github.com/camaraproject/WorkingGroups/blob/main/APIBacklog/documentation/SupportingDocuments/API%20proposals/APIproposal_WebRTC_Telefonica.md)) | Telefónica, Mavenir, Orange, Vodafone, TMUS | YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | | Network Insights | Verizon | 2023/08/31| [Link](https://github.com/camaraproject/WorkingGroups/pull/295) | Verizon, 5GFF, GSMA Open Gateway| YYYY/MM/DD | Under Evaluation | N/A | N/A | N/A | TBD | TBD | TBD | TBD | - + ## Attributes - `API [family] name`: it is the name of the API [family] proposal From 4b7eb0f484c38987c040e4a398897eb63119f45f Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Thu, 23 Nov 2023 14:46:35 +0100 Subject: [PATCH 6/6] Update APIproposal_DynamicPeopleDensityInformation_Telefonica.md --- ...proposal_DynamicPeopleDensityInformation_Telefonica.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md b/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md index 54f07e49..82346778 100644 --- a/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md +++ b/APIBacklog/documentation/SupportingDocuments/API proposals/APIproposal_DynamicPeopleDensityInformation_Telefonica.md @@ -2,11 +2,11 @@ | ---- | ----- | | API family name | Dynamic People Density Information | | API family owner | Telefonica | -| API summary | The service enables developers with the capability to get dynamic population density data in a specific area for a future date&time, considering anonymized information of the network connected devices in the requested area at the flight time.
Use Case (1): Providing BVLOS flight the data to meet SORA 2.5 requirements in terms of intrinsic Ground Risk Class (iGRC).
Use Case (2): Providing data to identify if the ground risk class for a given drone flight is acceptable for the time of the flight, or an alternative time should be considered to lower the risk.
Service Inputs: Area of the flight (delimited space).
Service Outputs: maximum population density value for the given area. | -| Technical viability | The viability has been checked and it is based on providing the amount of people on a flight path obtained by aggregating number of SIMs connected to each antenna on the path and without considering M2M SIMs, extrapolating to real-desnsity of population based on tht level of radio occupancy. No individual subscriber data will be delivered as the information will be anonymized. | -| Commercial viability | For use in drone flight scenarios, where population density is required to ensure a secure level of risk | +| API summary | The service enables developers with the capability to get dynamic population density data in a specific area for a future date&time, considering anonymized information of the network connected devices in the requested area at the flight time.
Use Case (1): Providing BVLOS flight the data to meet SORA 2.5 requirements in terms of intrinsic Ground Risk Class (iGRC).
Use Case (2): Providing data to identify if the ground risk class for a given drone flight is acceptable for the time of the flight, or an alternative time should be considered to lower the risk.
Service Inputs: Area of the flight (delimited space) and adjacent area. Date & time range.
Service Outputs: maximum population density value for the given area and adjacent area, and interval corresponding to the valid range of that value. (space and time maps) | +| Technical viability | The viability has been checked and it is based on providing the amount of people on a flight path obtained by aggregating number of SIMs connected to each antenna on the path and without considering M2M SIMs, extrapolating to real-desnsity of population based on tht level of radio occupancy. No individual subscriber data will be delivered as the information will be anonymized.
The output calculation will be defined as part of the API specification, in order to align on a common algorithm among telcos. The calculation will include
1. Aggregate number of devices/SIM cards connected to the mobile network, discriminating those that are classified as IoT/M2M. This relates with other APIs proposed.
2. Data prediction algorithm. Since the data is requested in a future moment, a prediction is requried to calculate the expected values, taht needs to be defined and agreed. For instance, a Basic implementation:  Average population in the past X weeks on same day-time, e.g. for a Tuesday 11:45, the number of people "attributed" to the area on the N preceding Tuesdays at the same time/hour.
3. Extrapolation of the people amount from the number of detected connected devices, also to be defined and agreed. MNO market share is a key parameter to design the extrapolation method.| +| Commercial viability | For use in drone flight scenarios, where population density is required to ensure a secure level of risk. | | YAML code available? | NO
To be provided | | Validated in lab/productive environments? | NO | | Validated with real customers? | NO | | Validated with operators? | YES
Proposal validates in OGW drop3 | -| Supporters in API Backlog Working Group | Telefonica; China Unicom (To align with RegionUserCount API) | \ No newline at end of file +| Supporters in API Backlog Working Group | Telefonica; China Unicom (To align with RegionUserCount API) |