Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Cluster data amount by region ids #146

Closed
oberinspector opened this issue May 25, 2020 · 3 comments
Closed

Cluster data amount by region ids #146

oberinspector opened this issue May 25, 2020 · 3 comments
Labels
backlog documentation Improvements or additions to documentation enhancement Improvement of an existing feature

Comments

@oberinspector
Copy link

Proposal:
Each app instance has an e.g. 2 byte region id which is provided or selected at time of installation. Large countries may have multiple regions and small countries maybe only 1 or 2. Goal ist to get almost equipartition regions related to population and expected infection rate. Also the regions must be large enough to respect the privacy of the users.

Each app sents own region id with the BT beacon and the receiving app seperates and collects all received region ids. So 2 Bytes of the BT payload would be needed to transfer own region id.

In case of infection and authorisation of a health organization the app uploads the EphIds of the acquisition period together with the own region id.

Apps retrieve only EphIds from infected individuals with the, during the acquisititon period, received region ids. For the vast majority of users this will only be one region id.

With this proposal it should be possible to have only one app for all participating countries and no national app solutions.

@oberinspector oberinspector added documentation Improvements or additions to documentation enhancement Improvement of an existing feature labels May 25, 2020
@oberinspector
Copy link
Author

Same as Cluster data amount by region ids at DP-3T

@tklingbeil
Copy link
Member

We have also thought about that.
However, broadcasting the region ID is currently not part of the Exposure Notification framework, so it's not possible to build this.

Having one single app for all countries is a completely different approach, which is out of our scope (as we are developing a national app).

@tkowark
Copy link
Member

tkowark commented May 25, 2020

Thanks for bringing up this idea, @oberinspector ! as tklingbeil mentioned, we are currently focused on the exposure notification framework. We will, however, closely monitor the discussions around the DP-3T issue you linked! To keep this repo focused on the current approach, I'd close this issue here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backlog documentation Improvements or additions to documentation enhancement Improvement of an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants